mechanism to enable interworking between network slicing and evolved packet core connectivity

专利摘要:
These are aspects of the present disclosure that refer to a mechanism to enable the interworking between the fifth generation system (5GS) network slicing and the evolved packet core (EPC) connectivity. In one example, techniques are provided for existing packet data unit (PDU) sessions that provide connectivity to a network slice in a set of network slices. Connectivity to the network slice is in response to user equipment (UE), which uses network slices, moving between a 5G network and a 4G network. Existing PDU sessions are connected to a dedicated core EPC network that supports the same services provided by the network slice.
公开号:BR112020007608A2
申请号:R112020007608-2
申请日:2018-08-31
公开日:2020-09-29
发明作者:Stefano Faccin；Haris Zisimopoulos；Sebastian Speicher
申请人:Qualcomm Incorporated；
IPC主号:

专利说明:

[0001] [0001] This claim claims the benefit of Non-Provisional Order Serial No. US 16 / 117,738, entitled "A MECHANISM TO ENABLE INTERWORKING BETWEEN NETWORK SLICING AND EVOLVED PACKET CORE CONNECTIVITY" filed on August 30, 2018, of Provisional Order serial number US 62 / 574,615, entitled "A MECHANISM TO ENABLE INTERWORKING BETWEEN 5GS NETWORK SLICING AND EPC CONNECTIVITY" filed on October 19, 2017, which is expressly incorporated in its entirety for reference in this document. BACKGROUND
[0002] [0002] Aspects of the present disclosure relate, in general, to wireless communication networks, and, more particularly, to a mechanism to enable interworking between the fifth generation system (5GS) network slicing and core connectivity evolved package (EPC).
[0003] [0003] Wireless communication networks are widely deployed to provide various types of communication content, such as voice, video, packet data, sending messages, broadcasting and so on. These systems can be multiple access systems that are capable of supporting communication with multiple users by sharing available system resources (for example, time, frequency and power). Examples of such multiple access systems include code division multiple access systems (CDMA), time division multiple access systems (TDMA), frequency division multiple access systems (FDMA), division multiple access systems orthogonal frequency (OFDMA) and single carrier frequency division multiple access system (SC-FDMA)
[0004] [0004] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that allows different wireless devices to communicate at the municipal, national, regional and even global levels. For example, a fifth generation (5G) wireless communication technology (which can be called a new radio (NR)) is expected to expand and support various usage scenarios and applications in relation to current mobile network generations. In one respect, 5G communications technology can include: improved mobile broadband that addresses human-centered use cases to access multimedia content, services and data; ultra-reliable, low-latency communications (URLLC) with certain specifications for latency and reliability; and massive machine-type communications, which can allow a large number of connected devices and transmit a relatively low volume of non-delay sensitive information. As demand for mobile broadband access continues to grow, however, further improvements in NR and other communications technology may be desired.
[0005] [0005] For example, for NR and other communications technology, the current interworking between 5GS and EPC network slicing (for example,
[0006] [0006] The following is a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all aspects covered, and is not intended to identify key or critical elements of all aspects or to outline the scope of any or all aspects. The sole purpose of this summary is to present some concepts of one or more aspects in a simplified way as a prelude to the more detailed description that is presented later.
[0007] [0007] In one aspect, the present disclosure includes techniques or mechanisms to enable interworking between 5GS network slicing and EPC connectivity (for example, support for 46) so that, for example, existing packet data (PDU) is maintained and not discarded when user equipment (UE) using network slices moves between a 5G network and a 4G network. In another aspect, the present disclosure includes techniques or mechanisms to enable interworking between 5GS network slicing and EPC connectivity (for example, support for 4G) so that, for example, the existing PDU sessions that provide connectivity to a network slice when an UE using network slices moves between a 5G network or a 4G network is connected to a dedicated EPC core network that supports the same services provided by the network slice.
[0008] [0008] In another aspect, a wireless communications method is described that includes enabling Network Slice Selection Policies (NSSP) to map applications to network slices, to a data network name (DNN) and to an access point name (APN) to be used when a UE is connected to an EPC, as an example when the APN used in the EPC is different from the DN used in a 5G network; and map the applications.
[0009] [0009] In another aspect, a wireless communications method is described that includes enabling the UE functionality to maintain a mapping between active packet network connections (PDN) and single network slice selection assistance information ( S-NSSAI) correspondents in response to the UE moving to an EPC or in response to the new PDN connections that are created while the UE is in the EPC; and provide information about mapping to an access and mobility management (AMF) function during a registration procedure.
[0010] [0010] In yet another aspect, a method of wireless communications is described that includes enabling an AMF that supports connectivity to a variety of network slices to be configured with a mapping between a set of network slices (for example , each identified by S-NSSAI) in a list of network slices allowed by the network for the UE (ie, in allowed S-NSSAI assigned to the UE) for a specific dedicated main network (DCN) in an EPC; and apply the mapping.
[0011] [0011] In another aspect, a wireless communications method is described that includes enabling a function management session selection (SMF) functionality to ensure that an AMF selects the SMF to establish a PDU session for a corresponding UE a network slice (for example, identified by S-NSSAI) considering a mapping between a set of network slices (for example, each identified by S-NSSAI) and the DCNs in the EPC, to ensure that the SMF can continue supporting PDU session connectivity management when the UE moves the PDU session to the EPC and a specific DCN is selected to serve the UE based on the mapping between the network slices and the DCNs; and apply SMF selection functionality.
[0012] [0012] In another aspect, a method of wireless communications is described which includes increasing an enrolled UE usage type maintained on a home subscriber server (HSS) with a temporary UE usage type defined by an AMF based on in S-NSSAI allowed; provide the type of temporary UE usage for the HSS when allowed S-NSSAIs are allocated to the UE; store, in the HSS, the type of temporary UE uses in addition to the type of registered UE uses; and, when providing the UE usage type to a mobility management entity (MME), if the HSS has a temporary UE usage type stored, the HSS provides the temporary UE usage type.
[0013] [0013] In another aspect, a wireless communication device is described that includes a transceiver, a memory and a processor in communication with the memory and with the transceiver, in which the processor is configured to perform any of the methods described in this document.
[0014] [0014] In yet another aspect, a wireless communication device is described that includes one or more means to perform any of the methods described in this document.
[0015] [0015] In yet another aspect, a computer-readable medium is described that stores computer code executable by a processor for wireless communications that includes one or more executable codes to perform any of the methods described in the present document.
[0016] [0016] In addition, the present disclosure also includes the apparatus that has components or configured to perform or means to perform of the methods described above, and the computer-readable medium that stores one or more codes executable by a processor to perform the methods described above.
[0017] [0017] For the accomplishment of the aforementioned and related purposes, the one or more aspects comprise resources from now on in this document and, particularly, mentioned in the claims. The following description and the accompanying drawings present in detail certain illustrative features of one or more aspects. These resources are indicative, however, of only a few ways in which the principles of various aspects can be employed, and it is intended that this description includes all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] [0018] The disclosed aspects will now be described in this document together with the accompanying drawings provided to illustrate and not to limit the disclosed aspects, in which similar designations denote similar elements, and in which:
[0019] [0019] Figure 1 is a schematic diagram of a wireless communication network that includes at least one user equipment (UE) that has an interworking component configured in accordance with this disclosure to interwork between the network slicing of the system. fifth generation (5GS) and evolved packet core connectivity (EPC);
[0020] [0020] Figure 2 is a block diagram that illustrates an example of an architecture without mobility for interworking between 5GS and EPC;
[0021] [0021] Figure 3 is a flow diagram of an example of a method for interworking between 5GS network slicing and EPC connectivity;
[0022] [0022] Figure 4 is a flow diagram of an example of another method for interworking between 5GS network slicing and EPC connectivity;
[0023] [0023] Figure 5 is a flow diagram of an example of another method for interworking between 5GS network slicing and EPC connectivity;
[0024] [0024] Figure 6 is a flow diagram of an example of another method for interworking between 5GS network slicing and EPC connectivity;
[0025] [0025] Figure 7 is a flow diagram of an example of yet another method for interworking between 5GS network slicing and EPC connectivity;
[0026] [0026] Figure 8 is a schematic diagram of exemplary components of the UE of Figure 1; and
[0027] [0027] Figure 9 is a schematic diagram of exemplary components of a network interconnection device to enable the interworking between 5GS network slicing and EPC connectivity. DETAILED DESCRIPTION
[0028] [0028] Several aspects are now described with reference to the drawings. In the following description, for the sake of explanation, numerous specific details are presented in order to provide a complete understanding of one or more aspects. However, it is evident that such an aspect (or aspects) can be practiced without these specific details. In addition, the term "component" as used in this document can be one of the parts that make up a system, can be hardware, firmware and / or software stored in a computer-readable medium, and can be divided into other components.
[0029] [0029] The present disclosure refers, in general, to techniques or mechanisms to enable the interworking between the fifth generation system (5GS) network slicing and the evolved packet core (EPC) connectivity (for example, support for fourth generation (4G6)) so that, for example, existing packet data unit (PDU) sessions are maintained and not discarded when user equipment (UE) using network slices moves between a 5G network and a 4G network. In another aspect, the present disclosure includes techniques or mechanisms to enable interworking between 5GS network slicing and EPC connectivity (for example, support for 4G) so that, for example, the existing PDU sessions that provide connectivity to a network slice when an UE using network slices moves between a 5G network or a 4G network and is connected to a dedicated EPC core network that supports the same services provided by the network slice.
[0030] [0030] With the introduction of the complex slicing feature in 5G networks, interworking with the EPC for devices on networks without full 5G radio access network (RAN) coverage or where some services are available only at the EPC needs to consider how the slicing functionality in the 5GC will work when the EPC: (1) does not support any core network concept, (2) supports Dedicated Core Networks (DCNs) through Decor, (3) supports DCNs through eDecor (ie Assisted Decor per EU). In particular, solutions are needed to: (1) define how a set of allowed network slices on the main 5G network (5GC) for a UE is mapped into a DCN when the UE moves to the EPC, how it is handled when the UE moves to an EPC without DCNs, (2) define how sets that can coexist in the 5GC, but map to different DCNs are handled in mobility to the EPC, and (3) define how EPC connectivity is mapped to slices of network when the UE moves from EPC to 5GC, since EPC has no concept of network slices and no network slicing context can be maintained or supported by EPC network functions.
[0031] [0031] The solutions described in this document for the issues observed introduce several components or aspects:
[0032] [0032] (1) Improve network slice selection (NSSP) policies to map not only applications to network slices (for example, single network slice selection assistance information (S-NSSAI)) and to a name data network (DNN), but also for the access point name (APN) to be used when the UE is in the EPC.
[0033] [0033] (2) Improve UE functionality to maintain mapping between active packet data connections (PDN) and corresponding S-NSSAIs when the UE moves to the EPC or when new PDN connections are created while the EU is in the EPC. The UE will use such information when moving from EPC to 5GC and provide it for the mobility and access management (AMF) function during a routing management (RM) procedure (for example, registration procedure).
[0034] [0034] (3) Improve the MFA to be configured with a mapping between a set of S-NSSAIs in the allowed S-NSSAIs assigned to a UE for a DCN in the EPC.
[0035] [0035] (4) Improve session management function selection (SMF) functionality to ensure that the AMF selects an SMF considering the mapping between S-NSSAIsS and DCNs.
[0036] [0036] (5) Ensure that the UE Use Type maintained on the home subscriber server (HSS) is increased with a Temporary UE Use Type defined by the AMF based on the permitted NSSAI, and sent to the HSS when the NSSAI allowed are allocated to the UE. When a mobility management entity (MME) requests the HSS UE Usage Type, if the Temporary UE Usage Type is defined, HSS provides that value. In this way, MME can select the DCN that serves the UE based on dynamic information and not just subscription information.
[0037] [0037] The additional features of the present aspects are described in more detail below in relation to Figures 1 to 9.
[0038] [0038] It should be noted that the techniques described in this document can be used for various wireless communications networks, such as code division multiple access (CDMA), time division multiple access (TDMA), multiple division access. frequency (FDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA) and other systems. The terms "system" and "network" are often used interchangeably. A CDMA system can implement radio technology, such as CDMAZ000, Universal Radio Land Access (UTRA), etc. CDMAZ2000 covers IS-2000, IS-95 and IS-856 standards. The versions of IS-2000 O and A can be commonly called CDMAZ000 IX, IX, etc. IS-856 (TIA-856) is commonly called CDMAZ0O0O I1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Broadband CDMA (WCDMA) and other CDMA variants. A TDMA system can implement radio technology, such as the Global System for Mobile Communications (GSM). An OFDMA system can implement radio technology, such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM ", etc. . O
[0039] [0039] The following description provides examples, and is not limited to the scope, applicability or examples presented in the claims. Changes can be made to the function and arrangement of elements discussed without departing from the scope of the disclosure. Several examples may omit, replace, or add various procedures or components as appropriate. For example, the methods described can be performed in a different order than described, and several steps can be added, omitted or combined. In addition, the resources described in relation to some examples can be combined into other examples.
[0040] [0040] With reference to Figure 1, according to various aspects of the present disclosure, an exemplary wireless communication network 100 includes at least one UE 110 with a modem 140 that has an interworking component 150 configured to support mechanisms to enable the interworking between 5GS network slicing and EPC connectivity. In some respects, the interworking component 150 may include one or more subcomponents including an application mapping component 152, a mapping management component 154, an SMF selection functionality component 156 and / or a usage type component 158. In one example, application mapping component 152 is configured to enable NSSPs to map applications to network slices, a DNN and an APN to be used when a UE is connected to an EPC, and to map the applications . In one example, mapping management component 154 is configured to enable the UE functionality to maintain a mapping between active PDN connections and the corresponding S-NSSAIs in response to the UE moving to an EPC or in response to new PDN connections that are created while the UE is in the EPC, and provide information about mapping to an AMF during a registration procedure. In another, the mapping management component 154 is configured to enable an access and mobility management (AMF) function that supports connectivity to a variety of network slices to be configured with a mapping between a set of network slices. network in a list of network slices allowed by the network to the UE for a specific dedicated main network (DCN) in an evolved packet core (EPC), apply the mapping.
[0041] [0041] In another example, the SMF 156 selection functionality component is configured to enable a session management function (SMF) selection feature to ensure that an access and mobility management (AMF) function selects one SMF to establish a packet data unit (PDU) session for user equipment (UE) corresponding to a network slice considering a mapping between a set of network slices and the dedicated main networks (DCNs) in a core evolved package (EPC), and apply the SMF selection functionality.
[0042] [0042] In another example, the usage type component 158 increases an enrolled user equipment (UE) usage type maintained on a home subscriber server (HSS) with a temporary UE usage type defined by a role management and mobility management (AMF) based on allowed network slice selection assistance information (S-NSSAI) allowed, and provides the type of temporary UE usage for HSS when allowed S-NSSAIs are allocated to the UE.
[0043] [0043] Additionally, wireless communication network 100 includes at least one network device (see, for example, Figure 9), a 950 interworking component (not shown) that performs network-related operations to support interworking between 5GS network slicing and EPC connectivity.
[0044] [0044] The wireless communication network 100 may include one or more base stations 105, one or more UEs 110, and a main network 115. The main network 115 can provide user authentication, access authorization, tracking, protocol connectivity. internet (IP) and other access, routing or mobility functions. The base stations 105 can interconnect with the main network 115 via links 120 (for example, SI, etc.). Base stations 105 can perform radio configuration and programming for communication with UEs 110, or they can operate under the control of a base station controller (not shown). In several examples, base stations 105 can communicate directly or indirectly (for example, through main network 115) with each other on return links 125 (for example, XI, etc.), which can be communication links wired or wireless.
[0045] [0045] Base stations 105 can communicate wirelessly with UEs 110 through one or more base station antennas. Each of the base stations 105 can provide communication coverage for a respective geographical coverage area 130. In some examples, base stations 105 can be called a transceiver base station, radio base station, access point, node access, radio transceiver, NodeB, eNodeB (eNB), gNB, Domestic NodeB, Domestic eNodeB, relay or some other suitable terminology. Geographic coverage area 130 for a base station 105 can be divided into sectors or cells that constitute only a portion of the coverage area (not shown). Wireless communication network 100 may include base stations 105 of different types (for example, macro stations or small cell base stations described below). In addition, the plurality of base stations 105 can operate according to different technologies than a plurality of communication technologies (for example, 5G (Radio Novo or "NR"), 4G / LTE, 3G, Wi-Fi, Bluetooth, etc. .), and thus can be overlapping coverage areas 130 for different communication technologies.
[0046] [0046] In some examples, the wireless communication network 100 may be or include or any combination of communication technologies, including an NR or 5G technology, an LTE, LTE-A or MuLTEfire technology, a Wi- Fi, a Bluetooth technology or any other long-range or short-range wireless communication technology. In LTE / LTE-A / MuLTEfire networks, the term evolved node B (eNB or e Node B) can, in general, be used to describe base stations 105 while the term UE can, in general, be used to describe the UEs 110. The wireless communication network 100 may be a heterogeneous technology network in which different types of eNBs provide coverage for various geographic regions. For example, each eNB or base station 105 can provide communication coverage for a macrocell, a small cell or other types of cell. The term "cell" is a 3GPP term that can be used to describe a base station, a carrier or a component carrier associated with a base station, or a coverage area (eg, sector, etc.) of a carrier or base station depending on the context.
[0047] [0047] A macrocell can, in general, cover a relatively large geographical area (for example, several kilometers in radius) and can allow unrestricted access by UEs 110 with service subscriptions with the network provider.
[0048] [0048] A small cell can include a base station powered by relative lower transmission when compared to a macrocell, which can operate in the same frequency bands or in different frequency bands (for example, licensed, unlicensed, etc.) like macrocells. Small cells can include picocells, femtocells and microcells according to several examples. A picocell can, for example, cover a small geographical area and can allow unrestricted access by UEs 110 with service subscriptions with the network provider. A femtocell can also cover a small geographical area (for example, a residence) and can provide restricted access and / or unrestricted access by the UEs 110 that have an association with the femtocell (for example, in the case of restricted access, the UEs 110 in one base station closed subscriber group (CSG) 105, which may include UEs 110 for users in the home and the like). An eNB for a macrocell can be called an eNB macro. A small cell eNB can be called a small cell eNB, eNB peak, eNB femto, or domestic eNB. An eNB can support one cell or multiple cells (for example, two, three, four and the like) (for example, component carriers).
[0049] [0049] The communication networks that can accommodate some of the various examples revealed may be packet-based networks that operate according to a stack of layered protocols and data on the user plane may be based on IP. A stack of user plan protocols (for example, packet data convergence protocol (PDCP), radio link control (RLC), MAC, etc.) can perform packet segmentation and reassembly and to communicate on logical channels . For example, a MAC layer can perform priority handling and multiplexing of logical channels in transport channels. The MAC layer can also use hybrid auto-retry request to provide retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer can provide establishment, configuration and maintenance of an RRC connection between an UE 110 and base stations 105. The RRC protocol layer can also be used for the main network support 115 radio bearer for user plan data. In the Physical layer (PHY), transport channels can be mapped to physical channels.
[0050] [0050] UEs 110 can be dispersed over wireless communication network 100, and each UE 110 can be stationary or mobile. A UE 110 may include or be called also by elements skilled in the art of mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, device remote, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, a client or some other suitable terminology. An UE 110 can be a cell phone, a smart phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a portable device, a tablet computer, a laptop computer, a cordless phone, smart watch, local wireless loop station (WLL), entertainment device, vehicle component, client facilities equipment (CPE) or any device that is capable of communicating on the communication network wireless 100. Additionally, an UE 110 can be Internet of Things (IoT) and / or machine-to-machine (M2M) type of device, for example, a type of low power device, low data rate (relative to a telephone wireless, for example), which can, in some respects, rarely communicate with the wireless communication network 100 or other UEs. An UE 110 may be able to communicate with various types of base stations 105 and network equipment including macro eNBs, small cell eNBs, macro gNBs, small cell gNBs, relay base stations and the like.
[0051] [0051] UE 110 can be configured to establish one or more wireless communication links 135 with one or more base stations 105. wireless communication links 135 shown on wireless communication network 100 can carry uplink transmissions (UL) from an UE 110 to a base station 105, or downlink transmissions (DL) from a base station 105 to an UE 110. Downlink transmissions can also be called direct link transmissions while transmissions uplink links can also be called reverse link transmissions. Each wireless communication link 135 can include one or more carriers, where each carrier can be a signal made up of multiple subcarriers (for example, waveform signals of different frequencies) modulated according to the various radio technologies described above . Each modulated signal can be sent on a different subcarrier and can carry control information (for example, reference signals, control channels, etc.), overload information, user data, etc. In one aspect, wireless communication links 135 can transmit bidirectional communications using frequency division duplexing (FDD) operation (for example, using paired spectrum resources) or time division duplexing ( TDD) (for example, using paired spectrum resources). Frame structures can be defined for FDD (for example, frame type 1) and for TDD (for example, frame type 2). In addition, in some respects, wireless communication links 135 may represent one or more broadcast channels.
[0052] [0052] In some aspects of the wireless communication network 100, base stations 105 or UEs 110 may include multiple antennas to employ antenna diversity schemes to improve the quality and reliability of communication between base stations 105 and the UEs 110. In addition or alternatively, base stations 105 or UEs 110 may employ multiple input and multiple output (MIMO) techniques that can take advantage of multipath environments to transmit multiple spatial layers that carry the same encoded data or data different coded.
[0053] [0053] The wireless communication network 100 can support operation in multiple cells or carriers, a feature that can be called carrier aggregation (CA) or operation of multiple carriers. A carrier can be called a component carrier (CC), layer, channel, etc. The terms "carrier", "component carrier", "cell" and "channel" can be used interchangeably in this document. A UE 110 can be configured with multiple downlink CCs and one or more uplink CCs for carrier aggregation. CA can be used with both FDD component carriers and TDD component carriers. Base stations 105 and UEs 110 can use bandwidth spectrum up to Y MHz (e.g., 5, 5, 10, 15, 20 MHz) per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x = number of component carriers) used for transmission in each direction. The carriers can be adjacent to each other or not. of carriers can be asymmetric in relation to DL and UL (for example, more or less carriers can be allocated to DL than to UL). CCs can include a primary CC and one or more secondary CCs. A primary CC can be called primary cell (PCell) and a secondary CC p It can be called a secondary cell (SCell).
[0054] [0054] Wireless communications network 100 may additionally include base stations 105 that operate in accordance with Wi-Fi technology, for example, Wi-Fi access points, in communication with UEs 110 that operate from according to Wi-Fi technology, for example, Wi-Fi stations (STAs) through communication links on an unlicensed frequency spectrum (for example, 5 GHz).
[0055] [0055] Additionally, one or more base stations 105 and / or UEs 110 can operate according to an NR or 5G technology called millimeter wave technology (mmW or mm wave). For example, mmW technology includes transmissions at mmW frequencies and / or nearby mmW frequencies. The extremely high frequency (EHF) is part of the radio frequency (RF) in the electromagnetic spectrum. The EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. The radio waves in this band can be called millimeter waves. Close to mmW it can exceed a frequency of 3 GHz with a wavelength of 100 mm. For example, the superhigh frequency band (SHF) extends between 3 GHz and 30 GHz, and can also be called a centimeter wave. Communications using the mmW radio frequency band and / or nearby mmW radio frequency band have extremely high path loss and a short range. Likewise, base stations 105 and / or UEs 110 that operate according to mmW technology can use beamforming in their transmissions to compensate for extremely high path loss and short range.
[0056] [0056] Additional details related to various aspects of techniques or mechanisms to enable the interworking between 5GS network slicing and EPC connectivity (for example, support for 4G) are described below.
[0057] [0057] For 4G systems, EPC supports main network or DECOR. This feature makes it possible for an operator to deploy multiple DCNs on a public land mobile network (PLMN) with each DCN consisting of a main network node or multiple network nodes (CN). Each DCN can be dedicated to serve specific type (or types) of subscriber. This is an optional feature and enables DCNs to deploy radio access technology or multiple radio access technologies (RATs) (for example, Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE ), Radio Access Network (GERAN), Universal Terrestrial Radio Access Network (UTRAN), UTRAN (E-UTRAN), Broadband E-UTRAN (WB-E- UTRAN) and Narrowband Internet of Things ( NB-IOT)). There may be various motivations for deploying DCNs, for example, to provide DCNs with specific characteristics / functions or scheduling, to isolate UEs or specific subscribers (for example, “machine to machine subscribers (M2M), subscribers belonging to a specific company or domain separate administrative body, etc.). It should be understood that a UE is, in general, connected to only one DCN at a time.
[0058] [0058] A DCN comprises one or more MME / support node (SGSN) of General Service Packet Radio Service (GPRS) and may comprise one or more service communication ports (SGWyPDN (PGW) communication port / policies and change rule function (PCRF).
[0059] [0059] In some deployment scenarios, networks that deploy DCNs may have a standard DCN, which is managing UEs for which a DCN is not available or if sufficient information is not available to assign a UE to a DCN. A DCN or multiple DCNs can be deployed in conjunction with a standard DCN where they all share the same RAN.
[0060] [0060] In some deployment scenarios, the architecture supports scenarios in which the DCN is only deployed in a part of the PLMN (for example, only for a RAT or only in a part of the PLMN area). Such heterogeneous or partial implantation of DCNs may, depending on the implantation and operator configuration, result in the service with different characteristics or functionality, depending on the possibility of the UE being inside or outside the service area or RAT that supports the DCN. In some instances, heterogeneous or partial implantation of DCNs can result in increased occurrence of UEs that are served first by a CN node in the standard DCN and then are redirected to a CN node in the DCN that serves the UE when the UE moves from the outer DCN coverage areas to a DCN coverage area. It can also result in an increased rate of re-attachment on the network. As this impacts the required capacity of the standard CN nodes deployed at the DCN coverage limit, it is not recommended to deploy heterogeneous or partially DCNs.
[0061] [0061] In some deployment scenarios, even if the DCN is not deployed to serve a particular RAT or PLMN service area, the UE in which the RAT or service area can still be served by a DCN PGW.
[0062] [0062] A high level overview for supporting DCNs is provided below. In some examples, an optional subscription information parameter ("UE Usage Type") is used when selecting a DCN. An operator configures which of its DCNs serves which Type (or Types) of UE Use. The HSS provides the "UE Usage Type" value in the UE subscription information for MME / SGSN. Both standardized values and operator-specific values for the EU Use Type are possible.
[0063] [0063] In some instances, the service network selects the DCN based on the operator-configured mapping (UE to DCN Use Type), the other policies of the locally configured operator and the context information related to the UE available on the network. service (for example, mobility information). UEs with different UE Type of Use values can be served by the same DCN. In addition, UEs that share the same UE Usage Type value for different DCNs.
[0064] [0064] In some examples, if the configuration does not show any DCN for the specific "EU Usage Type" value in the subscription information, then the service MME / SGSN serves the UE through the standard DCN or selects a DCN using specific service operator policies.
[0065] [0065] In some examples, the "UE Use Type" is associated with the UE (describing its usage characteristic), that is, there is only one "UE Use Type" per EU subscription.
[0066] [0066] In some examples, for each DCN, one or more NC nodes can be configured as part of a set.
[0067] [0067] In some examples, for MME, the MME Group Identification (or Identifications) (ID (or IDs)) or MMEGI (or MMEGIS) identifies a DCN in the PLMN. For SGSNs, a group identifier (or identifiers) identifies a DCN in the PLMN. That is, the group of SGSNs that belong to a DCN in a PLMN. This identifier can have the same format as the Network Resource Identifier (NRI) (for example, an NRI value that does not identify a specific SGSN node in the service area), in this case, it is called "Null-NRI", or it can have an independent NRI format, in which case it is called "SGSN Group ID". The "Null-NRI" or "SGSN Group ID" is provided by an SGSN to the RAN that triggers a Network Node Selection Function (NNSF) procedure to select an SGSN from the group of SGSNs corresponding to the Null -NRI / ID
[0068] [0068] In some examples, SGSN Group IDs make it possible to handle deployment scenarios in which, in a service area, all NRI values are allocated to SGSNs and therefore no NRI values remain that can be used like Null-NRI.
[0069] [0069] In some instances, the dedicated MME / SGSN serving the UE selects a dedicated S-GW and P-GW based on the EU's Type of Use.
[0070] [0070] In some examples, an initial access to the network if sufficient information is not available for RAN to select a specific DCN, the RAN can select a CN node from the standard DCN. Then, a redirect to another DCN may be required.
[0071] [0071] In some examples, to redirect a UE from a DCN to a different DCN, a redirection procedure via RAN can be used to forward a Strateless Access (NAS) message from the UE to the target DCN.
[0072] [0072] In some examples, all selection functions know DCN (or DCNs), including the NNSF of RAN nodes, to select and maintain the appropriate DCN for UEs.
[0073] [0073] There is also selection of dedicated main network assisted by UE or eDECOR. This feature is to reduce the need for DECOR rerouting by using an indication (DCN-ID) sent from the UE and used by the RAN to select the correct DCN. The DCN-ID can be assigned to the UE through the service PLMN and can be stored in the UE by PLMN ID. Both standardized values and operator-specific values for DCN-ID are possible. The UE can use the PLMN-specific DCN-ID whenever a PLMN-specific DCN-ID is stored for the target PLMN.
[0074] [0074] A domestic PLMN (HPLMN) can provision the UE with a single standardized DCN-ID that should be used by the UE only if it does not have any PLMN-specific DCN-ID of the target PLMN. When a UE configuration setting is changed with a new standardized standard DCN-ID, the UE must delete all PLMN-specific DCN-IDs.
[0075] [0075] The UE provides the DCN-ID for RAN in the registry in a new location in the network, that is, in the Fixation, TAU and RAU. The RAN selects the service node (MME or SGSN) based on the DCN-ID provided by the UE and the configuration on the RAN. For E-UTRAN, eNB is configured with DCNs supported by MMEs connected in the SI connection configuration. For UTRAN and GERAN, BSS / RNC is configured with DCNs supported on the SGSN connected via O&M. Both standardized DCN-IDs and PLMN-specific DCN-IDs can, in the RAN configuration, be assigned to the same network. If the information provided by the UE (for example, Globally Unique Temporary ID (GUTI), NRI, etc.) indicates a node (MME or SGSN) for attachment / TAU / RAU and a service node (MME or SGSN) corresponding to the information UEs can be found by the RAN node, the normal node selection must take precedence over the selection based on the DCN-ID. In the registry, MME / SGSN can verify that the correct DCN is selected. If the MME / SGSN concludes that the selected DCN is not the correct DCN, a DECOR rerouting is performed and the SGSN / MME in the new DCN assigns a new DCN-ID to the UE. The service MME / SGSN can also assign a new DCN-ID to the UE if, for example, the DCN-ID in the UE becomes obsolete or when the UE Usage Type is updated in the subscription information leading to a change in DCN. This is done as part of the GUTI Relocation procedure.
[0076] [0076] A network slice (or just a slice) is defined in a PLMN and includes the Main Network Control Plan and User Plan Network Functions, and, in the service PLMN, at least one of the following: a New Generation RAN (NG) or an Interfunctioning Function without 3GPP (N3IWF) for the Access Network without 3GPP. A network slice can be seen as a virtual end-to-end network (for example, network virtualization). A device, such as a UE, can connect to multiple network slices at the same time. Network slice instances can include instances for IoT, public security, eMBB and others. In addition, by enabling Network Slicing, an operator can provide services to different customers. For example, there may be an eMBB slice and / or a V2X slice that can be supported with the latter being possibly a specific automotive customer instance.
[0077] [0077] Network slices may differ for supported features and network function optimizations. The operator can deploy multiple instances of Network Slice that deliver exactly the same resources, but for different groups of UEs, for example, as they deliver a different commissioned service and / or because they can be dedicated to a customer.
[0078] [0078] A single UE can be served simultaneously by one or more instances of Network Slice through a 5G-AN. A single UE can be served, for example, by most of the eight Network Slices at a time. The AMF instance that serves the UE logically belongs to each of the instances of Network Slice that serves the UE, that is, that AMF instance is common to the instances of Network Slice that serve an UE. MFA can be seen as the common architectural point for several Network Slices.
[0079] [0079] The selection of the set of Network Slice instances, where each of the Network Slice instances can correspond to one or more Permitted S-NSSAIs, for a UE that is triggered by the first MFA normally contacted in a procedure record when interacting with the NSSF, and can lead to AMF change.
[0080] [0080] SMF discovery and selection in the Network Slice instance is initiated by the AMF when an SM message to establish a packet data unit (PDU) session is received from the UE. The NF repository function (NRF) is used to assist in the discovery and selection of network functions required for the Network Slice instance.
[0081] [0081] A PDU session belongs to one and only one instance of specific Network Slice per PLMN. Different Network Slice instances do not share a PDU session, although different slices may have slice-specific PDI sessions that use the same DNN.
[0082] [0082] In some respects, the identification and selection of a Network Slice is based on the S-NSSAI and NSSAI. In one example, S-NSSAIs identify a Network Slice. S-NSSAIs can be comprised of: a type of Slice / Service (SST), which refers to the expected Network Slice behavior in terms of resources and services and / or A Slice Differentiator (SD), which is optional information that complement the type (or types) of Slice / Service to differentiate between multiple multiple Network Slices of the same type of Slice / Service.
[0083] [0083] S-NSSAIs can have standard values or specific PLMN values. S-NSSAIs with specific PLMN values are associated with the PLMN ID of the PLMN that assigns them. S-NSSAIs should not be used by the UE in access layer procedures on any PLMN other than a PLMN to which the S-NSSAIs are associated.
[0084] [0084] NSSAIs are a collection of S-NSSAIs. There can be, for example, a maximum of 8 S-NSSAIsS in NSSAIs sent in signaling messages between the UE and the Network. Each S-NSSAI assists the network in selecting a particular Network Slice instance. The same instance of Network Slice can be selected through different S-NSSAIs. Based on the operator's operational and deployment needs, multiple instances of the Network Slice of certain S-NSSAI can be deployed in the same registration areas or in different registration areas. When multiple instances of the Network Slice of certain S-NSSAI are deployed in the same registration area, the AMF instance serving the UE may logically belong to more than one instance of the Network Slice of those S-NSSAI,
[0085] [0085] The selection of a Network Slice instance (or instances) serving a UE and the Main Network Control Plan and User Plan Network Functions corresponding to the Network Slice instance are the responsibilities of 5GC. (RAN can use Requested NSSAI in signaling access layer to handle UE Control Plan connection before 5GC informs (R) AN of Permitted NSSAI. Requested NSSAI is not used by RAN to route when UE it also provides a Temporary User ID.When a UE is successfully registered, the CN informs (R) AN when providing all Permitted NSSAIs for the Control Plan aspects.When a PDU session for certain S-NSSAIs is established using a specific Network Slice instance, the CN provides (R) AN with the S-NSSAI corresponding to that Network Slice instance to enable the RAN to perform specific access functions.
[0086] [0086] A UE can be configured by HPLMN with NSSAI Configured by PLMN. Configured NSSAIs can be PLMN specific and HPLMN indicates which PLMN (or PLMNs) each Configured NSSAI applies to, including whether the Configured NSSAI applies to all PLMNs, that is, Configured NSSAIs carry the same information regardless of PLMN that the UE is accessing (for example, it might be possible for NSSAISs that contain only standardized S-NSSAIs). When providing the Requested NSSAI to the network after registration, the UE in a given PLMN must use only S-NSSAIS belonging to the Configured NSSAI, if any, of that PLMN. Upon successful completion of an UE registration procedure, the UE may obtain from the AMF the Permitted NSSAIs for that PLMN, which may include one or more S-NSSAIs. These S-NSSAIs are valid for the current Registration Area provided by the service AMF where the UE was registered and can be used simultaneously by the UE (for example, up to the maximum number of Network Slices or PDU sessions). The UE may also obtain from the MFA one or more S-NSSAIs that are temporarily or permanently rejected.
[0087] [0087] Permitted NSSAIs can take precedence over Configured NSSAI for this PLMN. The UE may use only the S-NSSAI in the Permitted NSSAI corresponding to a Network Slice for subsequent procedures in the service PLMN.
[0088] [0088] In one aspect, the UE can store (S) NSSAISs based on the type of (S) NSSAI. For example, when the UE is provisioned with the NSSAI Configured for a PLMN in the UE, the Configured NSSAI can be stored in the UE until the new NSSAI Configured for that PLMN are provisioned in the UE by HPLMN: when provisioned with the new NSSAI Configured for a PLMN, the UE serves either to replace any Configured NSSAIs stored for that PLMN with the new Configured NSSAIs or to delete any Permitted NSSAIs and reject the S-NSSAIs for that PLMN.
[0089] [0089] In some examples, when the NSSAI Allowed for a PLMN is received, the NSSAI Allowed can be stored in the UE, including when the UE is turned off, until the new NSSAI Allowed for that PLMN are received. When the new Permitted NSSAIs for a PLMN are received, the UE can replace any stored Permitted NSSAIs for that PLMN with the new Permitted NSSAIs.
[0090] [0090] In some instances, when S-NSSAIs temporarily rejected for a PLMN are received, S-NSSAIs temporarily rejected can be stored in the UE as RM-REGISTERED.
[0091] [0091] In some instances, when S-NSSAIs permanently rejected for a PLMN are received, S-NSSAIs are permanently rejected in the UE as RM-REGISTERED.
[0092] [0092] An S-NSSAI or multiple S-NSSAIS in the Permitted NSSAIs provided to the UE may have non-standard values, which may not be a part of the UE's NSSAI configuration. In such cases, the Permitted NSSAI includes mapping information of how the S-NSSAIs in the Permitted S-NSSAIs correspond to the S-NSSAIs in the NSSAIs Configured in the UE. The UE uses this mapping information for its internal operation (for example, seeking an appropriate network slice for UE services). Specifically, an UE application, which is associated with the S-NSSAI as per NSSP, is additionally associated with the corresponding S-NSSAI of the Permitted NSSAI.
[0093] [0093] In some respects, the connectivity of the User Plan to a Data Network is established through an instance (or instances) of Network Slice. In one example, establishing User Plan connectivity to a Data Network through a Network Slice instance (or instances) comprises: performing an RM procedure to select an MFA that supports the required Network Slices and establishing a or more PDU sessions for the Data network required through the Network Slice Instance (or Instances).
[0094] [0094] In some respects, a Service AMF can be selected to support Network Slices. In one example, when a UE registers with a PLMN, if the UE for that PLMN has Configured NSSAI or Permitted NSSAI, the UE can provide the Requested NSSAI containing the S-NSSAI corresponding to the Network Slice (or Slices) to which the UE wishes to register, in addition to the Temporary User ID if assigned to the UE. Requested NSSAIs can be: (a) Configured NSSAIs, or a subset of them as described below, if the UE does not have any Permitted NSSAIs for the service PLMN; (b) the Permitted NSSAIs, or a subset of them as below, if there is no Permitted NSSAI for the service PLMN; or (c) the Permitted NSSAIs, or a subset thereof as described below, plus one or more Configured NSSAIs S-NSSAIs for which no corresponding S-NSSAIs are present in the Permitted NSSAIs and which have not previously been permanently rejected ( as defined below) across the network.
[0095] [0095] In some examples, the subset of configured NSSAIs provided in the Requested NSSAIs may consist of one or more S-NSSAIs in the Configured NSSAIs applicable to that PLMN, if the S-NSSAIs are not previously rejected permanently (as defined below) through the network, or are not previously added by the UE in the Requested NSSAI.
[0096] [0096] In some examples, the subset of Allowed NSSAI provided in the Requested NSSAI may consist of one more S-NSSAI in the latest NSSAI Allowed for that PLMN.
[0097] [0097] In one aspect, the UE can provide in the NSSAI Requested S-NSSAI of the Configured NSSAI that the UE previously provided for the service PLMN in this Registration Area if the S-NSSAI are not previously rejected permanently (as defined) below) over the network.
[0098] [0098] In some examples, the UE may include the NSSAI Requested in the RRC Connection Establishment and in the NAS messages. The RAN can route NAS signaling between that UE and a selected AMF using the Requested NSSAI obtained during the RRC Connection Establishment. If the RAN is unable to select an AMF based on the Requested NSSAIs, the RAN can route the NAS signaling to an AMF from a set of standard AMFs.
[0099] [0099] In some instances, when a UE registers with a PLMN, if, for that PLMN, the UE has no Configured NSSAI or Permitted NSSAI, the RAN can route all NAS signaling from / to that UE to / from a standard MFA. In an example, the UE may not indicate any NSSAI in the RRC Connection Establishment or in the Initial NAS message unless it has NSSAI Configured or NSSAI Allowed for the corresponding PLMN. Upon receiving Requested NSSAI from the UE and 5G-S-TMSI in RRC, if the RAN can reach an AMF corresponding to the 5G-S-TMSI, then the RAN can forward the request to that AMF. Otherwise, the RAN can select an appropriate AMF based on the Requested NSSAIs provided by the UE and can forward the request to the selected AMF. If the RAN is unable to select an AMF based on the Requested NSSAI, then the request can be sent to a standard AMF.
[0100] [0100] In one aspect, when an AMF selected by the NA receives the EU Initial Registration request: (a) the AMF, as part of the registration procedure, can consult the Unified Data Management (UDM) to retrieve information from EU signature including Signed S-NSSAIs; (b) AMF can verify whether S-NSSAIs in Requested NSSAIs are permitted on the basis of Signed S-NSSAIs; (c) the AMF, when the EU context in the AMF does not yet include Permitted NSSAI, you can consult the NSSF (see (B) below for further handling), except in the case where, based on the configuration in that AMF, it is allowed that the AMF determines whether it can serve the UE (see (A) below for subsequent handling). In one example, this setting may depend on the operator's policy; or (d) the AMF, when the context of UE in the AMF already includes Permitted NSSAI, based on the configuration for that AMF, can determine whether the AMF can serve the UE (see (A) below for further handling). This setting may depend on the operator's policy.
[0101] [0101] (A) Depending on the fulfillment of the configuration as described above, the MFA may be allowed to determine whether it can serve the UE, and the following can be done: The MFA can verify that the MFA can serve all S-NSSAI of Requested NSSAI present on Signed S-NSSAIs, or all S-NSSAI marked as standard on Signed S-NSSAIS in the event that no Requested NSSAI was provided. If that is the case, the MFA can remain the service MFA for the UE. Then, the Allowed NSSAIs can be made up of the list of S-NSSAIs in the Requested NSSAIs allowed based on the Signed S-NSSAIs, or, if no Requested NSSAIs are provided, all S-NSSAIs marked with the standard on the Signed S-NSSAIs ( see (C) below for subsequent handling). If this is not the case, the AMF may consult the NSSF (see (B) below for further handling).
[0102] [0102] (B) When AMF needs to consult the NSSF, as described above, the following can be done: the AMF can consult the NSSF, with the Requested NSSAI, the Signed S-NSSAIs, the SUPI PLMN ID, the information location and / or possibly access the technology that is used by the UE. Based on this information, local configuration and other locally available information including RAN capabilities in the Registration Area, NSSF can perform the following: (a) NSSF can select the Network Slice instance (or instances) to serve the UE . When multiple instances of Network Slice in the registration area are able to serve certain S-NSSAI based on the operator configuration, the NSSF can select one of them to serve the UE, or the NSSF can defer the selection of the Network until an NF / service in the Network Slice instance needs to be selected; (b) the NSSF may determine the target AMF Set to be used to serve the UE, or, based on the configuration, the list of candidate AMFs, possibly after consulting the NRF; (c) the NSSF can determine the Permitted NSSAI, also possibly considering the availability of the Network Slice instances that are capable of serving the S-NSSAI in the Permitted NSSAI in the current registration area; (d) based on an operator configuration, the NSSF can determine the NRF (or NRFs) to be used to select NFs / services contained in the selected Network Slice instance (or instances); (e) the NSSF may perform additional processing to determine the NSSAI Allowed in mobility scenarios; (f) the NSSF can return the Permitted NSSAI and the desired AMF Set to the current AMF, or, based on the configuration, the list of candidate AMFs. The NSSF can return the NRF (or NRFs) to be used to select NFs / services contained in the selected Network Slice instance (or instances). The NSSF may also return information related to the causes of rejection for S-NSSAI not included in the Permitted NSSAI that were part of the Requested NSSAI; (g) the AMF, depending on the information available and based on the configuration, can consult the NRF with the set of target AMFs. The NRF returns a list of candidate AMFs; or (h) the AMF, if forwarding to a target service AMF is required, you can forward the Registration Request to a target service AMF.
[0103] [0103] (C) The service MFA can return the Permitted NSSAI to the UE. The MFA may also refer to the UE for Requested S-NSSAIs not included in Permitted NSSAIs, if the rejection is permanent (for example, S-NSSAIs are not supported in PLMN) or temporary (for example, S-NSSAIs are not currently available in the Registration Area). After successful Registration, the UE may be provided with a Secondary Mobile Subscriber Identity
[0104] [0104] If the UE receives Permitted NSSAI from the service AMF, the UE can store these new Permitted NSSAI and replace any previously stored Permitted NSSAI for that PLMN.
[0105] [0105] In one aspect, the set of Network Slices for a UE can be modified. The set of Network slices for a UE can be changed at any time while the UE is registered in a network, and can be started by the network, or by the UE under certain conditions as described below. In some instances, the registration area allocated by the MFA to the UE may have homogeneous support for network slices.
[0106] [0106] The network, based on local policies changes to EU subscription and / or mobility, operational reasons (for example, an instance of Network Slice is no longer available), can change the set of Network Slices in which the UE is registered and provides the UE with new NSSAI Allowed. The network can make such a change during a Registration procedure or trigger a UE-facing notification of the change of Network Slices using a Generic UE Configuration Update procedure. Then, the new Permitted NSSAIs can be determined (an MFA Reallocation may be required). AMF can provide the UE with the new Permitted NSSAIs and the list of TAIS, and:
[0107] [0107] When a Network Slice used for one PDU session or multiple PDU sessions is no longer available to a UE, in addition to sending the new Allowed NSSAIs to the UE, the following may apply: (a) on the network, Network Slice is no longer available in the same MFA (for example, due to a change in subscription to
[0108] [0108] In some examples, the UE may use UE Configuration (for example, network slice security policy or NSSP) to determine whether traffic in progress can be routed through existing PDU sessions belonging to other Network Slices or You can establish the new PDU session (or sessions) associated with the same / other Network Slice.
[0109] [0109] In order to change the set of S-NSSAIsS that is used, the UE can initiate a Registration procedure.
[0110] [0110] Changing the set of S-NSSAISs in which the UE is registered (either UE or Network initiated) can lead to changes in MFA subject to operator policy.
[0111] [0111] In one aspect, MFA Reallocation can occur due to Network Slice Support (or Slices). In one example, during a PLMN Registration procedure, in the event that the network decides that the UE should be served by a different MFA based on aspects of the Network Slice (or Slices), then the MFA that first received the Registration Request you can redirect the Registration Request to another AMF through the RAN or by direct signaling between the initial AMF and the target AMF. The redirect message sent by the AMF through the RAN may include information for selecting a new AMF to serve the UE.
[0112] [0112] For a UE that is already registered, The system can support a redirection initiated by a UE's network from its service AMF to the target AME due to Network Slice (or Slice) considerations (for example, the operator has changed the mapping between the Network Slice instances and their respective service AMF (or AMFs) In some instances, the operator policy may determine whether redirection between AMFs is allowed.
[0113] [0113] In one aspect, a PDU session can be connected to a required Network Slice Instance (or Instances). Establishing a PDU session on a Network Slice for a DN allows data transmission on a Network Slice. A Data Network can be associated with S-NSSAI and a DNN.
[0114] [0114] In one example, the network operator (for example, HPLMN) can provision the UE with NSSP. NSSP's include one or more NSSP rules, each associating an application with certain S-NSSAI. A standard rule that matches all applications to the S-NSSAI can be included as well. When an UE application associated with specific S-NSSAIs requests data transmissions, then: if the UE has one or more established PDU sessions corresponding to the specific S-NSSAIs, the UE can route user data for that application in one of those sessions of PDU, unless other conditions in the UE prohibit the use of these PDU sessions. If the application provides a DNN, then the UE can also consider that DNN to determine which PDU session to use.
[0115] [0115] The UE can store the NSSP until new NSSP are provided to the UE by HPLMN. If the UE does not have a PDU session established with those specific S-NSSAIs, the UE can request a new PDU session corresponding to those S-NSSAIs and with the DNN that can be provided by the application. In order for the RAN to select an appropriate resource to support network slicing in the RAN, the RAN must be aware of the Network Slices used by the UE.
[0116] [0116] In one example, if a Network Slice instance is not selected during the Registration procedure for those specific S-NSSAIs, AMF can consult the NSSF with those specific S-NSSAIs, location information, PLMN ID's SUPI to select the Network Slice instance to serve the UE and to determine the NRF to be used to select NFs / services contained in the selected Network Slice instance.
[0117] [0117] In one example, the AMF can consult the NRF to select an SMF on a Network Slice instance based on the S-NSSAI, DNN and other information (for example, EU subscription and local operator policies) , when the UE triggers the establishment of a PDU session. The selected SMF can establish a PDU session based on the S-NSSAI and DNN.
[0118] [0118] In one example, when the MFA belongs to multiple Network Slices, based on the configuration, the MFA can use an NRF at the appropriate level for SMF selection.
[0119] [0119] In one aspect, Network Slicing can be performed through interworking with an evolved package system (EPS). A 5GC that supports Network Slicing may need to work with EPS on the 5GC PLMN or other PLMNs, and the EPC can support DCN in which MME selection can be assisted by a DCN-ID provided by the UE to the RAN . If the UE is in the EVOLIDED CM (ECM) or IDLE CM state, the mobility can trigger a Tracking Area Update (TAU) (or Attach, if it is in the first mobility event in the target system) in EPS and a 5GS Registration procedure. These procedures are sufficient to place the LV in the DCN or in the (set of) slice (or slices) of the right network.
[0120] [0120] For mobility / interworking 5GC in Connected mode for EPC and vice versa (for example, EPC for 5GC): when a CM state of UE in the AMF is CONNECTED by CM in the 5GC and a transfer to EPS occurs, the AMF can select the target MME and can forward the UE context to the selected MME in an MME-AMF interface (see, for example, Figure 2). Then, the transfer procedure can be performed. When the transfer is complete, the UE performs a TAU. This concludes the registration of UE in the target EPS and as part of this, the UE can obtain a DCN-ID if the target EPS uses the DCN-ID. It is open and can be implemented in different ways than how an MFA selects the target MME in the case of a transfer of UE from 5GC to an EPC that supports DCN.
[0121] [0121] The transfer between 5GC to EPC does not guarantee that all active PDU sessions of Network Slice (or Slices) can be transferred to EPC, so some PDU session (or sessions) can be discarded. When a UE is ECM CONNECTED at EPC, and performs a transfer to 5GS, MME can select the target AMF based on any available local information (including UE Use Type if an UE Use Type is available for the UE in the signature data) and can forward the UE context to the AMF selected in the MME-AMF interface. The transfer procedure is performed. When the transfer is complete, the UE can perform a Registration procedure. This concludes the registration of UE in 5GS and as part of this, the UE can obtain NSSAI Permitted. The possibility of having a limitation on the number of Network Slices supported by UE when interworking with EPS that is supported is open and can be implemented in different ways.
[0122] [0122] Figure 2 shows a diagram 200 that illustrates an example of an architecture without mobility 200 for the interworking between EPC 210 and 5GS 220. Several aspects described in this document in relation to an architecture without mobility can also apply to a mobility architecture.
[0123] [0123] In relation to Figure 2, architecture 200 can include a plurality of interfaces / points of reference between modules. The interfaces may include an MME-AMF 250 interface that is an interface between NCs between the MME 212 to 5GS AMF 222 in order to enable interworking between the EPC 210 and 5GS 220. As explained in further detail below, support for the MME-AMF 250 interface on the network is optional for interworking. In one example, the MME-AMF 250 interface can support a subset of the functionality (essential for interworking) that is supported at reference points (not shown) between MMEs for relocating MME and MME for transferring information from MME. These reference points can be used within PLMNs or between PLMNs (for example, in the case of HO between PLMNsS).
[0124] [0124] As shown in Figure 2, architecture 200 can also include a UDM + HSS 232 unit, a policy control function (PCF) + policy and change rules function (PCRF) 234, an SMF control + PGW (PGW-C) 236 and a user plan function (UPF) + PGW user (PGW-U) 238 dedicated for interworking between EPC 210 and 5GS 220. These units can be combined entities of EPC 210 and 5GS that support the respective functionalities for interworking. However, one or more of these units (for example, PCF + PCRF 234, SMF + PGW-C 236 and UPF + PGW-U 238) may be optional and may be based on the capabilities of one or more UEs 216, 226 and architecture
[0125] [0125] In one example, architecture 200 may also include another UPF (not shown in Figure 2) between NG-RAN 224 and UPF + PGW-U 238, that is, UPF + PGW-U 238 can support a reference point with an additional UPF, if necessary. Figure 2 and the procedures described in this document in conjunction with Figure 2 or similar architectures that depict a SGW 218 do not consider whether SGW 218 is deployed as a monolithic SGW or as a SGW division in its control plan functionality and user plan.
[0126] [0126] In order to interwork with EPC 210, an UE 216 or 226 that supports both 5GC 220 and EPC 210 (for example, supports both 5G and NR technologies as well as 4G technologies) can operate in single registration mode on dual registration mode.
[0127] [0127] In single registration mode, a UE can have only one mobility management (MM) state active (for example, RM state in 5GC 220 or EPS mobility management state (EMM) in EPC 210) and is in 5GC NAS mode or EPC NAS mode (when connected to 5GC 220 or EPC 210 respectively). The UE can maintain a single coordinated record for 5GC 220 and EPC 210.
[0128] [0128] In dual registration mode, the UE can handle independent registrations for 5GC 220 and EPC 210. In this mode, the UE can be registered only in 5GC 220, only in EPC 210 or both in 5GC 220 and EPC 210.
[0129] [0129] In one example, single registration mode support may be mandatory for UEs that support both 5GC NAS and EPC NAS.
[0130] [0130] In one example, during the E-UTRAN Initial Attachment procedure, a UE that supports both 5GC NAS and EPC NAS may need to indicate its 5G NAS support in UE Network Capability. For example, when registering with 5GC 220, the UE that supports both 5GC NAS and EPC NAS may need to indicate their EPC NAS support. This indication can be used to generate the priority for selecting SMF + PGW-C 236 for UEs that support both EPC NAS and 5GC NAS.
[0131] [0131] Networks that support interworking with EPC 210 may support interworking procedures that use the MME-AMF 250 interface or interworking procedures that do not use the MME-AMF 250 interface. Interworking procedures with the MME interface -AMF 250 can support the provision of IP address continuity in mobility between systems for UEs that support 5GC NAS and EPC NAS. Networks that support interworking procedures without the MME-AMF 250 interface can support "procedures for providing IP address continuity in mobility between systems for UEs operating in both single and double registration mode.
[0132] [0132] In some examples, the terms "initial attachment", "transfer attachment" and "" "TAU" for EU procedures in EPC 210 can be combined International Mobile Subscriber Identity Attachment (IMSL) / EPS and / or Tracking Area (TA) / Area - Location (LA) combined depending on UE configuration.
[0133] [0133] In one aspect, the interworking procedures with the use of the MME-AMF 250 interface can enable the exchange of MM states and session management (SM) between a source network and a target network. The transfer procedures can support with the MME-AMF 250 interface. When the interworking procedures with the MME-AMF 250 interface are used, the UE can operate in single registration mode. The network can retain only one MM status valid for the UE in AMF 222 or MME 212. In one example, AMF 222 or MME 212 is registered in HSS + UDM 232.
[0134] [0134] In some examples, support for the MME-AMF 250 interface between AMF 222 on 5GC 220 and MME 212 on EPC 210 may be necessary to enable continuous session continuity (for example, for voice services) for change between systems.
[0135] [0135] When the UE supports single registration mode and the network supports the interworking procedure with the MME-AMF 250 interface: (a) the UE, for idle mobility from 5GC 220 to EPC 210, can perform a TAU procedure with EPS GUTI mapped from the 5G-GUTI sent as a former Native GUTI. MME 212 can retrieve a 5GC 220 UE SM and MM context if the UE has an established PDU session or if the UE or EPC supports "attachment without PDN connectivity". The UE can perform an attachment procedure if the UE is registered without the PDU session on 5GC 220 and the UE or EPC 210 does not support attachment without PDN connectivity. For connected mode mobility from 5GC 220 to EPC 210, a transfer between systems can be performed. During the TAU or Attachment procedure, HSS + UDM 232 can cancel any AMF registration; and (b) the UE, for idle mobility from EPC 210 to 5GC 220, can perform a registration procedure with EPS GUTI sent as the former GUTI. The AMF 222 and the SMF + PGW-C 236 can retrieve the EU SM and MM context from EPC 210. For connected mode mobility from EPC 220 to 5GC 210, a transfer between systems can be performed. During the Registration procedure, HSS + UDM 232 can cancel any MME registration.
[0136] [0136] In some examples, interworking can occur without the MME-AMF interface
[0137] [0137] Interworking procedures without the MME-AMF 250 interface can use the following two items: (1) When PDU sessions are created on the 5GC 220, the SMF + PGW-C 236 can update its information along with the DNN in the HSS + UDM 232; or HSS + UDM 232 can provide information about dynamically allocated SMF + PGW-C information and APN / DNN information for the target CN network.
[0138] [0138] In some examples, to support mobility for UEs in dual registration mode, the following additional items can also be supported by the network: (3) MME 212, when the UE performs the Initial Attachment on EPC 210 and provides a indication that the old node was an AMF 222, it may not include an "initial attachment" indicator for HSS + UDM 232. This may result in HSS + UDM 232 not canceling the registration of AMF 222, if any; (4) AMF 222, when the UE performs the Initial Registration on 5GC 220 and provides EPS GUTI, it may not include an "initial attachment" indicator for HSS + UDM 232. This may result in HSS + UDM 232 not canceling the registration of MME 212, if any; or (5) MME 212, when PDN connections are created on EPC 210, it can store SMF + PGW-C information and APN information on HSS + UDM 232.
[0139] [0139] In some instances, the network may support item 3 above to provide IP address retention for UEs operating in single registration mode when the UE moves from 5GC 220 to EPC 210. In some examples, the The network can support items 4 and 5 described above together with item 6 described below to provide IP address retention for UEs operating in single registration mode when the UE moves from EPC 210 to 5GC 220. In item (6 ) below, AMF 222, when the UE performs Mobility Registration on the 5GC 220 and provides an EPS GUTI, can determine that the old node is the MME 212 and can proceed with the procedure and provide an indication of "Session Configuration Transfer with Supported EPC "to the UE in the Registration Acceptance message.
[0140] [0140] In one aspect, mobility can be provided for UEs in single registration mode.
[0141] [0141] In one aspect, mobility can be provided for UEs in dual registration mode. For example, to support mobility in dual registration mode, MME-AMF 250 interface support between AMF 204 in 5GC and MME 202 in EPC may not be required. Instead, for the UE operating in dual registration mode, the following principles may apply to the transfer of a PDU session from 5GC to the EPC: (a) the UE operating in Dual Registration mode can register in the EPC prior to any PDU session transfer using the Attach procedure without establishing a PDN Connection on the EPC if the EPC supports EPS Attachment without PDN Connectivity. In some examples, support for EPS Attachment without PDN Connectivity may be mandatory for an UE that supports dual registration procedures. Before attempting prior registration with the EPC, the UE may need to verify that the EPC supports EPS Attachment without PDN Connectivity by reading the SIB related to the target cell; (b) the UE may perform a PDU session transfer from the 5GC to the EPC using the PDN connection establishment procedure initiated by the UE with an indication of "transfer" in the PDN Connection Request message; (c) if the UE did not register with the EPC prior to the transfer of the PDU session, the UE may perform Attachment to the EPC with an indication of "transfer" in the PDN Connection Request message; (d) the UE can selectively transfer certain PDU sessions to EPC, while maintaining other PDU sessions on
[0142] [0142] In one aspect, for the UE operating in dual registration mode, the following principles may apply to the transfer of PDN connection from EPC to 5GC: (a) a UE operating in Dual Registration mode can register with 5GC prior to any PDN connection transfer using the Registration procedure without establishing a PDU session at 5GC; (b) a UE may perform a PDN connection transfer from the EPC to 5GC using the PDU session establishment procedure initiated by the UE with an indication of "Existing PDU session"; (c) the UE, if the UE did not register with the 5GC prior to the transfer of the PDN connection, it can perform the 5GC Registration with an indication of "Existing PDU Session" in the PDU Session Request message. In some instances, Registration support combined with PDU Session Request may still be open and can be implemented in different ways; (d) the UE may selectively transfer certain PDN connections to 5GC, while maintaining other PDN Connections in the EPC; (e) the UE may keep the registration updated in both the EPC and 5GC by periodically re-registering in both systems. In some instances, if the EPC or 5GC record times out (for example, after the attainable mobile timer expires), the corresponding network may initiate an implicit decoupled timer. In one example, whether the UE transfers some or all of the PDN connections on the 5GC side and whether the UE keeps the record updated on both the 5GC and the EPC may depend on the UE capabilities that are dependent on implementation. In some examples, information to determine which PDN connections are transferred on the 5GC side and triggers can be preconfigured in the UE. In one example, if the EPC does not support EPS Attachment without PDN Connectivity, MME 202 can couple with the UE when the last PDN connection is released by PGW (in relation to the transfer of the last PDN connection to access without 3GPP); or (f) the network, when sending a control plan request to Mobile Telecommunications (MT) services (for example, MT SMS), can route the control plan through the EPC or 5GC. In some instances, in the absence of an UE response, the network may attempt to route the control plan request through another system. In one example, the choice of system through which the network tries to deliver the control plan request first can be determined by the network configuration.
[0143] [0143] In view of the above descriptions related to the use of dedicated core networks (DCNs) in the
[0144] [0144] With this implementation of Network Slicing mechanisms in 5GC networks, three scenarios need to be considered for the interworking between 5GC and EPC: (1) interworking with EPC that does not support Decor or eDecor; (2) interworking with EPC that supports Decor; and (3) interworking with EPC that supports eDecor
[0145] [0145] Furthermore, considering the 5GC / EPC interworking solutions, it is relevant to consider the following cases: (1) a single record UE on a network that supports an MME-AMF interface; (2) a single registration UE on a network that supports double registration (without an MME-AMF interface); and (3) a dual registration UE on a network that supports double registration.
[0146] [0146] The implantation of Network Slices in the 5GC may need to be coordinated by an operator with the DCNs that the operator EPC supports. Multiple scenarios may need to be considered, for example, (a) each 5GC Network Slice may correspond to a specific DCN (ie 1: mapping 1); and (b) multiple 5GC Network Slices correspond to a specific DCN (ie, N: mapping 1)
[0147] [0147] In one example, if two Network Slices are "mutually exclusive" in 5GC (for example, the UE can be connected to one slice or the other slice), these two Network Slices are expected to correspond to different DCNs in the EPC.
[0148] [0148] The questions for these combinations of scenarios can be summarized as follows: (a) The EPC has no concept of Network Slicing, and does not understand that the information used by the UE and 5GC to support Network Slicing ; (b) if the support for multiple Network Slices has slice coexistence issues (ie, not all Network Slices that the UE has signed can be supported simultaneously by an AMF, and therefore no service AMF can support any combinations of Network Slices for the UE), then specific MFAs may need to be selected to serve the UE for a subset of the Network Slices that the UE subscribes to. This was addressed in the definition of slicing mechanisms when returning to the UE NSSAI Allowed, in which the network ensures that the S-NSSAIs (slices) in the NSSAI Allowed can coexist. However, when a UE moves to the EPC after establishing connectivity to a set of Network Slices on the 5GC, or when the UE first establishes connectivity on the EPC: (1) the EPC, without Decor and eDecor, may not support all connections of PDNs that correspond to the Network Slices that the UE needs to connect, or (2) in the EPC, with Decor or eDecor, there cannot be any DCN that supports all the Network Slices that the UE needs to connect to.
[0149] [0149] This means that when the UE moves from 5GC to EPC or when a 5GC UE, configured to support multiple slicing and mapping applications / services for Network Slices, first establishes connectivity to the EPC, appropriate connectivity may need be provided by EPC without Decor, or an appropriate DCN can be selected for the UE. This means that: (a) when moving from 5GC to EPC without Decor, the PDU sessions corresponding to the Network Slices to which the UE has established user plan connectivity in 5GC may need to be moved to the EPC. In one example, not all such PDUs can be supported by the EPC, and some PDUs can be discarded / discarded. In one example, while in the EPC, the UE can activate additional PDN connections. In some instances, when the UE moves to 5GC, 5GC may not have context information that maps the active PDN connection to the appropriate slices, and therefore 5GC may not be able to: (1) select one Appropriate service AMF to support the required Network Slices, or (2) "distribute" active PDU sessions to the Network Slices that the UE needs to connect to; and (b) when moving from 5GC to EPC with Decor or eDecor, in addition to the problem listed above, a correct DCN may need to be selected to be the UE. In one example, it may need to be possible both in the case of transfer and in the case of mobility in idle mode.
[0150] [0150] The following steps describe problems created by current methods to resolve the issues described above. In one aspect, "if the UE is in an ECM OLEOUS or CM OLEOUS state, the mobility triggers a TAU (or Attachment, if it is the first mobility event on the target system) in EPS and a 5GS Registration procedure. These procedures are sufficient to place the UE in the right DCN or (set of) Network Slice (or Slices). However, this presentation is not entirely correct or accurate. In fact, the following may need to be considered: (a) for idle mobility from EPC to 5GC: In EPC (independently without, in the case of single radio, the UE first registered with 5GC and then moved to EPC, or first registered with EPC), the UE may have a set of PDN connections, each corresponding to an APN. These PDN connections can correspond to PDU sessions transferred from 5GC, or established directly at the EPC, or a combination of both. If operators use generic APNs, or specific APNs / dedicated slices for sliced connectivity and specific, and have corresponding APNs for use in EPC, then (1) in the case of a single registration UE and no MME-AMF interface, when the UE performs a 5GC Registration, the UE can provide the required Requested NSSAIs thus, the correct MFA and the set of slices can be selected; (2) in the case of dual registration, when the UE performs a 5GC Registration, the UE can provide the required Requested NSSAIs, thus the correct MFA and set of slices can be selected; or (3) however, in the case of a single record UE and the MME-AMF interface, when the UE performs a Record at 5GC and the context is retrieved from the MME, the AMF can receive only one context containing the sessions PDU and the corresponding APNs, but may not receive any slicing information that would identify the Network Slices that the UE needs to connect to (in order to support active PDU sessions), or the mapping between PDU sessions and any slices .
[0151] [0151] In another aspect, "when an EU CM state in the AMF is CONNECTED by CM in the 5GC and a transfer to EPS occurs, the AMF selects the target MME and forwards the UE context to a selected MME in the Interface MME-AMF ". The EPC can select the AMF based only on the location of the target 5G-RAN node, without any slicing considerations: this implies that the AMF that is selected as a "generic AMF" that needs to be able to simultaneously support all sessions of PDU potentially corresponding 'to different slices in order to facilitate mobility. Once the UE performs the Registration procedure at the end of the transfer, the UE may provide the actual Requested NSSAI, and an AMF reallocation may need to take place. However, 5GC needs to implement such "generic AMFsS" to make the transfer feasible.
[0152] [0152] In another aspect, "when a UE is CONNECTED BY in EPC, and performs a transfer to 5GS. When the Transfer is completed, the UE performs a Registration procedure. This concludes the registration of UE in the target 5GS and, as part of that, the UE gets NSSAI Allowed ". In the case where multiple 5GC slices correspond to a specific DCN, when the UE is connected to the EPC for a given DCN with one or more active PDN connections, unless explicit information is provided at a certain time to the 5GC in the mobility of the EPC for 5GC, 5GC may have no way of knowing which slice a particular PDU session corresponds to. This can be particularly true if a given APN can apply to multiple S-NSSAIs (that is, specific APNs with no slice).
[0153] [0153] In another aspect, "UE operating in Dual Record mode can register with the EPC prior to any PDU session transfer using the Attach procedure without establishing a PDN Connection on the EPC if the EPC supports the EPS attachment without
[0154] [0154] In another aspect, the "UE operating in Dual Registration mode can register with 5GC prior to any transfer of PDN connection using the Registration procedure without establishing a PDU session at 5GC. The UE performs transfer of PDN connection from EPC to 5GC using the PDU session establishment procedure initiated by UE with "indication of Existing PDU Session". If eDECOR is not used, but the network supports DCNs, the UE cannot have no knowledge of the selected DCN for the UE In order to move the established PDN connection to the correct slices based on the Requested NSSAI, the UE provides in the 5GC Registration procedure: (a) There may be a need for a match between the DCN selected in the EPC and the slice set in the 5GC At a minimum, the correct PGW / SMF node may need to be selected if the PDN connections are established in the EPC, to ensure that the PGW / SMF is part of the appropriate slice; or (b) there may be a need there is a correspondence between the APN used in the EPC for PDN connections and the combination of "APNH + S-NSSAI" used for a PDU session in 5GC; or (c) The same can be applied to the text that states that "if the UE did not register with the 5GC prior to the transfer of the PDN connection, the UE may perform the 5GC Registration with an indication of" Existing PDU Session "in the message PDU Session Request ”.
[0155] [0155] In another aspect, when a UE performs an attachment or TAU on the EPC and no DCN information is available, the MME can be selected by the RAN according to other factors. If this corresponds to a scenario in which a single record UE is idle from 5GC to EPC, the selected MME may not belong to the correct DCN to serve the UE based on active PDU sessions and corresponding slices in the 5GC . According to the currently standardized mechanism for DCCs in EPC: (a) if the MME does not have enough information to determine whether it can serve the UE, the MME can send an Authentication Information Request message to the HSS requesting the Use Type of EU. The HSS, if it supports DCNs, can provide the UE Usage Type in the Authentication Information Reply message. Therefore, the MME can decide whether to serve the UE or whether an MME in a different DCN needs to be selected. However, the UE Usage Type stored in the HSS is a semi-static configuration parameter that may not correspond to the active slice set for the UE in the 5GC. This is particularly true for devices that sign a variety of slices, including slices that cannot coexist; or (b) in the case of idle mobility of a UE between MMEs or idle mode mobility of a single record UE between an MFA and the MME, the target MME receives the MM and SM context of the target node after the UE triggers the MM procedure (for example, TAU) and the RAN selects the MME. However, in such scenarios, no mechanism is defined for the selected MME to determine whether it can serve the UE or whether redirection to another MME based on the MM / SM context is required.
[0156] [0156] Various solutions are described below that provide techniques or mechanisms to enable the interworking between 5GS network slicing and EPC connectivity. These solutions involve one or more of the following: (a) improving NSSP policies to not only map applications to slices (ie, S-NSSAI) and to the DNN, but also to the APN to be used when the UE is in the EPC; (b) improving the UE functionality to maintain the mapping between active PDN connections and the corresponding S-NSSAIs when the UE moves to the EPC or when new PDN connections are created while the UE is in the EPC. The UE can use such information when moving from EPC to 5GC and will provide the same information to MFA during an MR procedure (for example, Registration procedure); (c) improve the MFA to be configured with a mapping between a set of S-NSSAIS in the Permitted S-NSSAIs assigned to a UE for a DCN in the EPC; (d) improve the SMF / PGW-C selection functionality to ensure that the AMF selects an SMF considering the mapping between the S-NSSAIS in the Permitted NSSAI and the DCNs in the EPC to ensure that the selected SMF / PGW-C is part DCN mapped from the Permitted NSSAI; or (e) ensure that the UE Usage Type maintained in the HSS is increased with the Temporary UE Usage Type defined by the MFA based on the Permitted NSSAIs, and sent to the HSS when the Permitted NSSAIs are allocated to the UE. When an MME requests the HSS UE Usage Type, if the Temporary UE Usage Type is defined, the HSS provides that value. In this way, MME can select the DCN that serves the UE based on dynamic information and not just subscription information.
[0157] [0157] In more detail, the solutions described above involve one or more mechanisms. In one aspect, (1) connections maintained by UE can be mapped to slice information. In one example, when connecting to a 5GC with network slicing, the UE can use the NSSP configured to select the S-NSSAI (and DNN) to be used for an application. In combination with Configured NSSAIs, you can enable the UE to build the Requested NSSAIs needed to support services / applications in the UE. In order to enable interworking with EPC, the UE may maintain a mapping, for each active PDU session, of the <DNN, S-NSSAI> to a PDU Session ID for each active PDU session. In some examples, the UE may receive the corresponding NSSAIs in a Protocol Configuration Option (PCO) field in response to a new PDN connection that is created while the UE is in the EPC.
[0158] [0158] In some examples, for each mapping from <DNN, S-NSSAI> to an application / service, NSSP can also contain the mapping to an APN to be used by the UE when connected to the EPC (ie when the UE establishes a PDN connection while connected to the EPC with 3GPP access connected to the EPC or via non-3GPP access (for example, through unreliable non-3GPP or an ePDG)), if the APN used in the EPC is different from the DNN used at 5GC. In this way, a single mapping of applications and connectivity can exist in the UE.
[0159] [0159] In some instances, when the UE first establishes PDU sessions through the 5GC and then moves the PDU sessions to the EPC, to the PDU sessions that are moved to the EPC (a selective set in the case of a Dual registration UE, or the set of PDU sessions that are supported in the EPC after mobility for EPC), the UE can maintain for each PDN connection the mapping between the <DNN, S-NSSAI> and the Session ID of PDU that would apply to that PDU session in the 5GC, and to the corresponding APN for the PDN connection in the EPC. This can be particularly important for established PDN connections while the UE is connected to the EPC.
[0160] [0160] In some instances, when UE moves from EPC to 5GC (for example, for single record UE, it applies to idle mobility and MME-AMF interface transfer; to dual radio UE , applies to registration performed at 5GC when the UE is connected to the EPC, before the UE moves the PDN connections or when the UE triggers the mobility of the first PDN connection to the 5GS), the UE can provide S mapping - NSSAIs for PDU session IDs, and possibly the mapping of PDU session IDs to the related DNN for 5GC in NAS mobility management messages (for example, Registration Request) in addition to the Requested NSSAI. This can make it possible for the MFA to receive such information “to identify which Network Slices correspond to the PDN connections that were active for The UE in the EPC.
[0161] [0161] In another aspect, (2) as an alternative to (1) above, when the UE moves from 5GC to EPC, the UE can supply MME in NAS MM procedures (eg TAU) a "Slicing Information Container" that can contain a mapping between the PDU sessions and the corresponding slices (that is, mapping from PDU Session ID to S-NSSAI). MME may not interpret such information, but it may store it. In some instances, the UE may update the information in the MME each time a PDN connection is added or dropped (including if the transfer of PDU sessions from 5GC to the EPC results in some PDU sessions being dropped). In some instances, in the case of transferring the EPC to 5GC, or when the AMF recovers the context of the MME in idle mobility, the MME can supply the stored container to the AMF. The AMF can use the information on the container to map the PDU sessions to the appropriate slices (ie, S-NSSAI).
[0162] [0162] In another aspect, (3) in addition to the previous solutions, for scenarios where a single record UE first connects to 5GC, then moves to EPC, and returns to 5GC, instead of providing in RRC signaling to 5G GUTI previously allocated by the AMF, the UE can supply only the NSSAIs Requested based on the slice set required by the UE, in order to enable the RAN to select an AMF that can serve the slice set to which the UE connects. Meanwhile, the UE can provide 5G GUTI in NAS signaling.
[0163] [0163] In yet another aspect, (4) a UE that has registered with an AMF that indicates the ability to connect to the EPC, when an SMF is selected during the creation of the PDU session (for example, by the AMF or NSSF or NRF), the entire SMF selection can consider the mapping between S-NSSAIsS and DCNs in SMF selection. The consideration of the mapping can be done to enable the selection of an SMF / PGW-C that is in the correct DCN in order to support mobility for the EPC. For example, if S-NSSAIs mapped to DCN1 and S-NSSAI2 mapped to DCN2, when an SMF is selected for a PDU session corresponding to S-NSSAIl, a SMF / PGW combo for S-NSSAIl that belongs to DCNl may need to be selected.
[0164] [0164] In yet another aspect, (5) when an MME receives an attachment or TAU from a UE that is previously registered on a main network node (for example, AMF) identified by the temporary identifier of
[0165] [0165] In yet another aspect, (6) an alternative to (5), for each subscriber on a network that deploys both EPC and 5GC, the common HSS / UDM node can store a UE Usage Type. The HSS can also store a Current UE Usage Type value that is defined by an MFA.
[0166] [0166] In some examples, AMF can be configured with information mapping to map combinations of S-NSSAIs to Type of Use values.
[0167] [0167] In some instances, when the AMF allocates Permitted NSSAIs to the UE, the AMF can also send the UE Use Type mapped to the HSS, and the HSS can store the UE Use Type mapped as the Use Type Current EU
[0168] [0168] In some instances, when an MME retrieves the UE Use Type from the UE, if the HSS has a Current UE Use Type stored, the HSS can provide the UE with the Current UE Use Type. This can help an MME to determine whether the MME can serve an UE when an UE performs an attachment or TAU procedure with the MME after having established a context with the MFA. In this way, the MME can select a service MME corresponding to the DCN that supports the slices to which the UE is connected in the 5GC.
[0169] [0169] In some examples, optionally, when the HSS receives a new Temporary UE Usage Type value and determines that the UE has a record in the 5GC and a record in the EPC, the HSS may trigger an update of the Usage Type of EU for MME. After receiving such an update, MME can store the EU Use Type received and can remember that the EU Use Type has been modified. After the UE performs signaling towards the MME, the MME can determine whether the MME can serve the UE based on the type of UE usage received and, if not, the MME triggers an MME reallocation for a new service MME.
[0170] [0170] With reference to Figure 3, a flow diagram of an example of a method 300 is shown according to the aspects described above for the interworking between 5GS network slicing and EPC connectivity, where method 300 includes one or more of the actions defined in this document.
[0171] [0171] For example, in 302, method 300 may include making it possible for NSSPs to map applications to network slices, a DNN and an APN to be used when a UE is in the EPC. As an example, when the APN used in EPC is different from the DNN used in 5GS. For example,
[0172] [0172] In 304, method 300 includes mapping applications. For example, in one aspect, one or more of the devices described in this document can perform actions at 304.
[0173] [0173] In 306, method 300 optionally includes maintaining a mapping of network slices, DN and APN to a packet data unit (PDU) session identity (ID) for each active PDU session. For example, in one aspect, one or more of the devices described in this document can perform the actions in
[0174] [0174] With reference to Figure 4, a flow diagram of an example of a 400 method is shown according to the aspects described above for fe) interworking between 5GS network slicing and EPC connectivity, where the method 400 includes one or more of the actions defined in this document.
[0175] [0175] For example, in 402, method 400 includes enabling the UE functionality to maintain a mapping between active PDN connections and the corresponding S-NSSAIs in response to UEs moving to an EPC or in response to new connections of PDN that are created while the UE is in the EPC. For example, in one aspect, one or more of the devices described in this document can perform actions at 402. As used in this document, the terms PDN connections and PDU session are equivalent and can be used interchangeably.
[0176] [0176] In 404, method 400 includes providing information about the mapping to an MFA during a registration procedure. For example, in one aspect, one or more of the devices described in this document can perform the actions in 404.
[0177] [0177] With reference to Figure 5, a flow diagram of an example of a method 500 is shown according to the aspects described above for the interworking between 5GS network slicing and EPC connectivity, where method 500 includes one or more of the actions defined in this document.
[0178] [0178] For example, in 502, method 500 includes enabling an MFA to support connectivity with a variety of network slices to be configured with a mapping between a set of network slices (for example, each can be identified by S-NSSAIs) in a list of network slices allowed by the network for the UE (that is, in the allowed S-NSSAIs assigned to a UE) for a specific DCN in an EPC. For example, in one aspect, one or more of the devices described in this document can perform actions at 502. As described in this document, a network slice is a slice identified by S-NSSAI, an allowed network slice is a slice identified by permitted NSSAI, and, similarly, for other network slices.
[0179] [0179] In 504, method 500 includes applying the mapping. For example, in one aspect, one or more of the devices described in this document can perform the actions at 504.
[0180] [0180] With reference to Figure 6, a flow diagram of an example of a 600 method is shown according to the aspects described above for the interworking between 5GS network slicing and EPC connectivity, where the 600 method includes one or more of the actions defined in this document.
[0181] [0181] For example, in 602, method 600 includes enabling a function management session selection (SMF) feature to ensure that an AMF selects an SMF to establish a PDU session for a UE corresponding to a network slice (for example, identified by S-NSSAI) considering a mapping between a set of network slices (for example, identified by S-NSSAIs) and the DCNs in the EPC, to ensure that SMF can continue to support connectivity management to the PDU session when the UE moves the PDU session to the EPC and a specific DCN is selected to serve the UE based on the mapping between the network slices and the DCNs. For example, in one aspect, one or more of the devices described in this document can perform actions on
[0182] [0182] In 604, method 600 includes applying SMF selection functionality. For example, in one aspect, one or more of the devices described in this document can perform the actions at 604.
[0183] [0183] Referring to Figure 7, a flow diagram of an example of a 700 method is shown according to the aspects described above for the interworking between 5GS network slicing and EPC connectivity, where the 700 method includes one or more of the actions defined in this document.
[0184] [0184] For example, in 702, method 700 includes increasing an enrolled UE usage type maintained in an HSS with a temporary UE usage type defined by an MFA based on permitted S-NSSAIs. For example, in one aspect, one or more of the devices described in this document can perform actions at 702.
[0185] [0185] In 704, method 700 includes providing the temporary UE usage type for the HSS when the allowed S-NSSAIs are allocated to the UE. For example, in one aspect, one or more of the devices described in this document can perform actions at 704.
[0186] [0186] In 706, method 700 optionally includes storing, in the HSS, the type of temporary UE usage in addition to the enrolled UE usage type.
[0187] [0187] In 708, method 700 optionally includes, when providing the UE usage type for an MME, if the HSS has a temporary UE usage type stored, the HSS provided the temporary UE usage type.
[0188] [0188] With reference to Figure 8, an example of an implementation of UE 110 may include a variety of components, some of which have already been described above, but including components such as one or more 812 processors and 816 memory and 802 transceiver communicating over one or more 844 buses, which can operate in conjunction with modem 140 and interworking component 150 to enable one or more of the functions described in this document related to mechanisms that enable interworking between 5GS network slicing and connectivity of EPC. Additionally, the one or more processors 812, the modem 140, the memory 816, the transceiver 802, the front interface of RF 888 and one or more antennas 865 can be configured to support voice and / or data calls (simultaneously or not simultaneously) ) on one or more radio access technologies.
[0189] [0189] In one aspect, the one or more 812 processors may include modem 140 which uses one or more modem processors. The various functions related to the interworking component 150 can be included in the modem 140 and / or processors 812 and, in one aspect, can be performed by a single processor, while in other aspects, different functions between the functions can be performed by a combination two or more different processors. For example, in one aspect, the one or more 812 processors may include any or any combination of a modem processor, or a baseband processor or a digital signal processor, or a broadcast processor, or a receiver, or a transceiver processor associated with the 802 transceiver. In other respects, some of the features of the one or more processors 812 and / or modem 140 associated with the interworking component 150 can be realized by the 802 transceiver.
[0190] [0190] In addition, memory 816 can be configured to store data used in this document and / or local versions of 875 applications or interworking component 150 and / or one or more of its subcomponents that are run by at least one 812 processor The 816 memory can include any type of computer-readable medium usable by a computer or at least an 812 processor, such as random access memory (RAM), read-only memory (ROM), tapes, magnetic disks, optical discs, memory volatile, non-volatile memory and any combination thereof. In one aspect, for example, memory 816 may be a non-transitory computer-readable storage medium that stores one or more computer executable codes that define the interworking component 150 and / or one or more of its subcomponents, and / or data associated therewith, when the UE 110 operates at least one processor 812 to execute the interworking component 150 and / or one or more of its subcomponents. The interworking component 150 can include one or more subcomponents configured to perform at least part of the actions described above in conjunction with methods 300, 400, 500, 600 and / or 700.
[0191] [0191] The 802 transceiver may include at least one receiver 806 and at least one transmitter 808. The receiver 806 may include hardware code, firmware and / or software executable by a processor to receive data, the code comprising instructions and is stored in a memory (for example, computer readable medium). The 806 receiver can be, for example, a radio frequency (RF) receiver. In one aspect, the 806 receiver can receive signals transmitted by at least one base station
[0192] [0192] Furthermore, in one aspect, the UE 110 may include the RF 888 front interface, which can operate in communication with one or more 865 antennas and the 802 transceiver to receive and transmit radio transmissions, for example, wireless communications. wire transmitted by at least one base station 125 or wireless transmissions transmitted by UE 110. The RF 888 front interface can be connected to one or more 865 antennas and may include one or more 890 low-noise amplifiers (LNAs), one or more switches 892, one or more power amplifiers (PAs) 898 and one or more filters 896 for transmitting and receiving RF signals.
[0193] [0193] In one aspect, LNA 890 can amplify a signal received at a desired output level. In one respect, each LNA 890 can have specified minimum and maximum gain values. In one aspect, the RF 888 front interface can use one or more 892 keys to select a specific 890 LNA and its specified gain value based on a desired gain value for a specific application.
[0194] [0194] Additionally, for example, one or more 898 APs can be used by the RF 888 front interface to amplify a signal to an RF output at a desired health power level. In one respect, each PA 898 can have specified minimum and maximum gain values. In one aspect, the RF 888 front interface can use one or more 892 keys to select a specific PA 898 and its specified gain value based on a desired gain value for a specific application.
[0195] [0195] In addition, for example, one or more 896 filters can be used by the front RF interface 888 to filter a received signal to obtain an incoming RF signal. Similarly, in one aspect, for example, a respective filter 896 can be used to filter an output from a respective PA 898 to produce an output signal for transmission. In one aspect, each 896 filter can be connected to a specific LNA 890 and / or PA 898. In one aspect, the RF 888 front interface can use one or more 892 switches to select a transmit and receive path using a specified 896, LNA 890 and / or PA 898 filter, based on a configuration as specified by 802 transceiver and / or processor
[0196] [0196] Thus, the 802 transceiver can be configured to transmit and receive wireless signals through one or more 865 antennas via the RF 888 front interface. In one aspect, the transceiver can be tuned to operate at specified frequencies, so that UE 110 can communicate with, for example, one or more base stations 125 or one or more cells associated with one or more base stations 125. In one aspect, for example, modem 140 can configure the transceiver 802 to operate at a specified frequency and power level based on the UE configuration of UE 110 and the communication protocol used by modem 140.
[0197] [0197] In one aspect, modem 140 may be a multi-band, multi-mode modem that can process digital data and communicate with the 802 transceiver, so that digital data is sent and received using the 802 transceiver. In one aspect, modem 140 can have multiple bands and be configured to support multiple frequency bands for a specific communications protocol. In one aspect, modem 140 can have multiple modes and be configured to support multiple operational networks and communications protocols. In one aspect, modem 140 can control one or more components of UE 110 (e.g., RF 888 front interface, 802 transceiver) to enable transmission and / or reception of network signals based on a specified modem configuration. In one aspect, the configuration of the modem can be based on the mode of the modem and the frequency band in use. In another aspect, the modem configuration can be based on UE configuration information associated with the UE 110 as provided by the network during cell selection and / or cell reselection.
[0198] [0198] Referring to Figure 9, an example of an implementation of a 900 network device can include a variety of components, some of which have already been described above, but including components, such as one or more 912 processors and 916 memory and transceiver 902, in communication through one or more buses 944, which can operate in conjunction with an interworking component 950 to enable one or more of the functions described in this document related to network side operations associated with mechanisms that enable interworking between slicing 5GS network and EPC connectivity. In one example, the network device 900 can implement at least part of the functionality of an AMF or MME (see Figure 2), where that functionality is related to network side operations associated with mechanisms that enable interworking between the 5GS network slicing and EPC connectivity
[0199] [0199] Transceiver 902, receiver 906, transmitter 908, one or more processors 912, memory 916, applications 975 and buses 944 can be the same or similar to the corresponding components of UE 110 as described above, but configured or otherwise mode, scheduled for network side operations as opposed to UE operations. Transceiver 902 can be configured to support an interface such as the MME-AMF interface described above in conjunction with Figure 2.
[0200] [0200] The above detailed description in conjunction with the accompanying drawings describes examples and does not represent only the examples that can be implemented or that are within the scope of the claims. The term "example", when used in this description, means "serving as an example, instance or illustration", not "preferred" or "advantageous over other examples". The detailed description includes specific details for the purpose of providing an understanding of the techniques described. However, these techniques can be practiced without these specific details. In some instances, well-known structures and devices are shown as a block diagram in order to avoid obscuring the concepts of the examples described.
[0201] [0201] Information and signals can be represented using any of a variety of technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols and chips that can be referenced throughout the description above can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, code or computer-executable instructions stored in a computer-readable medium or any combination thereof.
[0202] [0202] the various blocks and illustrative components described in conjunction with the disclosure in this document can be implemented or carried out with a specially programmed device, such as, but not limited to, a processor, a digital signal processor (DSP), an ASIC , an FPGA or other programmable logic device, discrete gate element or transistor logic, discrete hardware component or any combination thereof designed to perform the functions described in this document. A specially programmed processor can be a microprocessor, but, alternatively, the processor can be any conventional processor, controller, microcontroller or state machine. A specially programmed processor can also be implemented as a combination of computing devices (for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core or any other such configuration).
[0203] [0203] The functions described in this document can be implemented in hardware, software executed by a processor, firmware or any combination thereof. If implemented in software run by a processor, the functions can be stored or transmitted as one or more instructions or code in a non-transitory, computer readable medium. Other examples and implementations are within the scope and spirit of the disclosure and the attached claims. For example, due to the nature of software, the functions described above can be implemented using software executed by a specially programmed processor, hardware, firmware, wiring or combinations of any of these. Features that implement functions can also be physically located in various positions, including distributed so that portions of functions are implemented in different physical locations. In addition, as used herein, including in the claims, "or" as used in a list of items preceded by "at least one of" indicates a disjunctive list so that, for example, a list of "at least one among A , B or C "means A or B or C or AB or AC or BC or ABC (that is, A and BeC).
[0204] [0204] Computer-readable media includes both computer storage media and communication media including any medium that facilitates the transfer of a computer program from one place to another. A A storage medium can be any available medium that can be accessed by a general purpose or special purpose computer. For example, and without limitation, computer-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage device, or any other medium that can be used to load or store program code of the desired code in the form of instructions or data structures and which can be accessed by a general purpose or special purpose computer or by a general purpose or special purpose processor. In addition, any connection is properly called a computer-readable medium. For example, if the software is transmitted from a web page, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies, such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio and microwave are included in the definition of medium. The magnetic disk and the optical disk, as used in this document, include CD, laser disk, optical disk, digital versatile disk (DVD), floppy disk and Blu-ray type disk in which the magnetic disks usually reproduce data magnetically while the optical discs optically reproduce data with lasers. The combinations of the above are also included in the scope of computer-readable media.
[0205] [0205] The prior description of the disclosure is provided to enable an element skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the common principles defined in this document can be applied to other variations without departing from the scope of the disclosure.
Additionally, although the elements of the described aspects and / or modalities can be described or claimed in the singular, the plural is contemplated unless the limitation to the singular is explicitly presented.
In addition, all or a portion of any aspect and / or embodiment may be used with all or a portion of any other aspect and / or embodiment, unless otherwise stated.
Thus, the disclosure should not be limited to the examples and projects described in this document, but should be in accordance with the broader scope consistent with the innovative principles and resources disclosed in this document.

权利要求:
Claims (32)
[1]
1. Wireless communications method comprising: enabling network slice network selection (NSSP) policies to map applications to network slices, a data network name (DNN) and an access point name (APN) to be used when user equipment (UE) is connected to an evolved packet core (EPC); and map the applications.
[2]
2. Method according to claim 1, in which the APN used in the EPC is different from the DNN used in a fifth generation main network (5GC).
[3]
3. Method, according to claim 1, in which the enabling of the NSSP to map applications to network slices is performed in response to the UE that connects to the 5GC.
[4]
4. Method according to claim 1, which further comprises maintaining a mapping of network slices, DNN and APN to a packet data unit (PDU) session identity (ID) for each active PDU session .
[5]
5. Wireless communications method comprising: enabling user equipment (UE) functionality to maintain a mapping between active packet data network (PDN) connections and single network slice selection assistance information ( S-NSSAI) correspondents in response to a UE moving to an evolved packet core (EPC) or in response to the new PDN connections that are created while the UE is in the EPC; and provide information about mapping to an access and mobility management (AMF) function during a registration procedure.
[6]
A method according to claim 5, wherein a PDN connection is the same or similar to a packet data unit (PDU) session.
[7]
7. Method according to claim 5, which further comprises: receiving the corresponding S-NSSAIs in a Configuration Option field (PCO) in response to the new PDN connection that is created while the UE is in the EPC.
[8]
8. Wireless communications method comprising: enabling an access and mobility management (AMF) function that supports connectivity to a variety of network slices to be configured with a mapping between a set of network slices in a list of network slices allowed by the network to the UE for a specific dedicated main network (DCN) in an evolved packet core (EPC); and apply the mapping.
[9]
A method according to claim 8, wherein a network slice of the network slice set is identified by assistance information from the selection of a single network slice (S-NSSAI).
[10]
A method according to claim 9, wherein a permitted network slice is identified by permitted S-NSSAIs.
[11]
11. Method according to claim 9, wherein the S-NSSAIs are used by the AMF in order to select a session management function (SMF) corresponding to the network slice.
[12]
12. Wireless communications method comprising: enabling a session management role selection (SMF) feature to ensure that an access and mobility management (AMF) role selects an SMF to establish a packet unit session. data (PDU) for a user equipment (UE) corresponding to a network slice considering a mapping between a set of network slices and the dedicated main networks (DCNs) in an evolved packet core (EPC); and apply SMF selection functionality.
[13]
13. Method according to claim 11, in which the mapping ensures that the SMF continues to support PDU session connectivity management when the UE moves the PDU session to the EPC and a specific DCN is selected to serve the UE based on the mapping between the network slice set and the DCNs
[14]
14. Wireless communications method comprising: increasing a type of enrolled user equipment (UE) usage maintained on a home subscriber server (HSS) with a temporary UE usage type defined by an access management function and mobility (MFA) based on allowed assistance information for selecting a single slice of network (S-NSSAI) allowed; and provide the temporary UE usage type for the O HSS when allowed S-NSSAIs are allocated to the UE.
[15]
15. Method according to claim 14, which further comprises storing, in the HSS, the type of temporary UE usage in addition to the enrolled UE usage type.
[16]
16. Method according to claim 15, in which, when providing the UE usage type to a mobility management entity (MME), if the HSS has a temporary UE usage type stored, the HSS provides the type of temporary EU use.
[17]
17. Wireless communication device comprising: a memory that stores instructions; and a processor in communication with memory, where the processor is configured to execute instructions to: enable network slice selection (NSSP) policies to map applications to network slices, to a data network name (DNN ) and for an access point name (APN) to be used when user equipment (UE) is connected to an evolved packet core (EPC); and map the applications.
[18]
18. Wireless communication device according to claim 17, in which the APN used in the EPC is different from the DNN used in a fifth generation main network (5GC).
[19]
19. Wireless communication device according to claim 17, in which the processor is additionally configured to enable NSSPs to map applications to network slices in response to the UE that connects to the 5GC.
[20]
20. Wireless communication device according to claim 17, wherein the processor is additionally configured to maintain a mapping of network slices, DNN and APN to a packet data unit session identity (ID) (PDU) for each active PDU session.
[21]
21. Wireless communication device comprising: a memory that stores instructions; and a processor communicating with memory, where the processor is configured to execute instructions to: enable the user equipment (UE) functionality to maintain a mapping between active packet data network (PDN) connections and those corresponding network slice selection assistance information (S-NSSAI) in response to a UE moving to an evolved packet core (EPC) or in response to new PDN connections that are created while the UE is in the EPC ; and provide information about mapping to an access and mobility management (AMF) function during a registration procedure.
[22]
22. A wireless communication device according to claim 21, wherein a PDN connection is the same or similar to a packet data unit (PDU) session.
[23]
23. Wireless communication device according to claim 21, wherein the processor is additionally configured to execute the instructions to: receive the corresponding S-NSSAI in a Configuration Option (PCO) field in response to the new connection PDN that is created while the wireless communication device is in the EPC.
[24]
24. Wireless communication device comprising: a memory that stores instructions; and a processor in communication with memory, where the processor is configured to execute instructions to: enable an access and mobility management (AMF) function that supports connectivity to a variety of network slices to be configured with a mapping enter a set of network slices in a list of network slices allowed by the network to the UE for a specific dedicated main network (DCN) in an evolved packet core (EPC); and apply the mapping.
[25]
25. Wireless communication device according to claim 24, wherein a network slice of the set of network slices is identified by assistance information from the selection of a single network slice (S-NSSAI).
[26]
26. Wireless communication device according to claim 25, wherein a permitted network slice is identified by permitted S-NSSAI.
[27]
27. Wireless communication device according to claim 25, wherein the S-NSSAIs are used by the AMF in order to select a session management function (SMF) corresponding to the network slice.
[28]
28. Wireless communication device comprising: a memory that stores instructions; and a processor communicating with memory, where the processor is configured to execute instructions to: enable a session management role selection (SMF) feature to ensure that an access and mobility management (AMF) role selects an SMF to establish a data packet unit (PDU) session for a user device (UE) corresponding to a network slice considering a mapping between a set of network slices and the dedicated core networks (DCNs) in a core evolved package (EPC); and apply SMF selection functionality.
[29]
29. Wireless communication device according to claim 24, where the mapping ensures that the SMF continues to support connectivity management to the PDU session when the UE moves the PDU session to the EPC and a specific DCN is selected to serve the UE based on the mapping between the set of network slices and the DCNs.
[30]
30. Wireless communication device comprising: a memory that stores instructions; and a processor in communication with the memory, where the processor is configured to execute the instructions to: increase a type of enrollment of user equipment (UE) maintained on a home subscriber server (HSS) with a type of use of Temporary UE defined by an access and mobility management (MFA) function based on permitted network slice selection assistance information (S-NSSAI); and provide the temporary EU usage type for the O
HSS when allowed S-NSSAIs are allocated to the UE.
[31]
31. Wireless communication device according to claim 30, wherein the processor is additionally configured to store, in the HSS, the temporary UE usage type in addition to the enrolled UE usage type.
[32]
32. Wireless communication device according to claim 30, in which, when providing the UE usage type to a mobility management entity (MME), if the HSS has a temporary UE usage type stored, the HSS provides the temporary UE usage type.
1/9; X. Í% ”C o. 2 the 8 VW is 8 | 3 8 8 = Give E the 2 8 H! 7 õ = s SW o f s o o É 6 o É he 8
2 ... AT S IS SZ and Ss I / O i gs IS THIS RS) Z E S already = | 2 21 Ss B = io; Fools | 82 | E & | & ET do- E + z => // 8sS | Ã% o FR E | = | o% E ko o i h o o vo 2 2nd o ”ii | o /> oe = // 7o PS oi "> = | 2 [| 28 | 28 € |% ico cs E ooio 2 io oo F i =: Ss to Ss sº |; bas) = E oo E 8 ij j 5 SEE 5 Í 8 8 Õ NO. i; Õ Õ O | == / 8 E i = 2 E a
OS A: A À 8 SÁ E i / À VON jd A / e is Ao = / Oo jr, EBNTAÃ | | es a PN Ee i bus; SG: Í o | nor: toan O a; 4 / x 2 À ==:; 3 IT TA TO WO)! met 48 1 i K | << PT i us | TSE! ; : Fo AN IT o À '- oO á 1 - == À FE DP = i E o ó oi (TE / i SO BN =:: EN: TOTAL ": i
E FR h =) | o VV SR o! SN; 6 lille is o:; / VT 2 is: Deo NA NAT VT 7 AS) À 1: ES AZ = io meo À E o: À PN o. Í À E 2 í wo | / Po: y $ TE: oO -
TETTTTTTTTTTTTTA MD | B | | $ | <í o) = HZAASS | EE BN | | S | | | | | | |
SS So | | | | a EN EN | | 8 & z Hollow Edo | o O = O E TT 2 IES E a a Q & + ll + É | | 5 E & o 3 8 | | | | | E | 3 | | | õ Zz ”What if! S&S ts | = s 5 Ss! | + 5 | ———) ——————————— | RM 2) oO
QN

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112020007608A2|2020-09-29|mechanism to enable interworking between network slicing and evolved packet core connectivity

---

CN110301154B|2021-07-20|Method and apparatus for optimized user plane anchoring

---

KR102164230B1|2020-10-12|Terminal registration method and apparatus therefor in wireless communication system

---

KR102047708B1|2019-11-22|Method and network device for responding to request

---

EP2950589B1|2018-02-07|Method of handling access network discovery and selection function and related communication device

---

US11160134B2|2021-10-26|Method for performing RRC connection procedure in wireless communication system and apparatus therefor

---

US11160014B2|2021-10-26|Connection gateway selection in a mobile communications device

---

US10609744B2|2020-03-31|Method for direct communication between terminals in wireless communication system and apparatus for method

---

CN109076437B|2021-11-30|System information transmission method, base station, system information receiving method and user equipment

---

EP3641423A1|2020-04-22|Method for registering terminal in wireless communication system and apparatus therefor

---

CN106576234B|2020-02-18|Sending cellular related paging messages over non-cellular RAT

---

US20190239147A1|2019-08-01|Method for connecting to network and user equipment

---

KR20170044656A|2017-04-25|Enhanced ue registration and paging

---

US20200275331A1|2020-08-27|Method for transmitting and receiving signal related to handover from 5gs to eps in wireless communication system and device therefor

---

CN107211342B|2020-08-07|Method for selecting P L MN by terminal in wireless communication system and device thereof

---

CN111357339A|2020-06-30|Method for transmitting and receiving signal related to handover access in wireless communication system and apparatus therefor

同族专利:

---

公开号 | 公开日

---

TW201924400A|2019-06-16|

---

US20190124561A1|2019-04-25|

---

EP3698587A1|2020-08-26|

---

US11026128B2|2021-06-01|

---

CA3075021A1|2019-04-25|

---

CN111226472A|2020-06-02|

---

JP2021500800A|2021-01-07|

---

KR20200068668A|2020-06-15|

---

US20210258836A1|2021-08-19|

---

WO2019078964A1|2019-04-25|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

US10897507B2|2016-04-01|2021-01-19|Qualcomm Incorporated|Mechanism to enable connectivity sessions and IP session establishment|

---

WO2018008980A1|2016-07-05|2018-01-11|엘지전자|Method for selecting resource operation preferred by user in wireless communication system and device for same|

---

WO2018069852A1|2016-10-11|2018-04-19|Telefonaktiebolaget Lm Ericsson |Network slicing-aware access network|

---

US10299094B2|2017-01-31|2019-05-21|Verizon Patent And Licensing Inc.|HSS-based application authorization for machine-type-communications|

---

US11140621B2|2017-05-08|2021-10-05|Motorola Mobility Llc|Methods and apparatuses for reconfiguring a data connection|

---

JP2019525506A|2017-06-19|2019-09-05|華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ．|Registration method, session establishment method, terminal, and AMF entity|

---

US10986567B2|2017-06-20|2021-04-20|Motorola Mobility Llc|Creating a network slice selection policy rule|

---

US11160134B2|2017-08-09|2021-10-26|Lg Electronics Inc.|Method for performing RRC connection procedure in wireless communication system and apparatus therefor|

---

EP3474601A1|2017-10-17|2019-04-24|HTC Corporation|Device and method of handling a protocol data unit session and a network slice|KR20180044012A|2016-10-21|2018-05-02|삼성전자주식회사|Mehotd and apparatus for connecting network to terminal based on applicable network information in mobile communication system|

---

US10848238B1|2017-02-13|2020-11-24|Lockheed Martin Corporation|Evolved packet system over non-LTE radio access network|

---

CN108632808A|2017-03-17|2018-10-09|华为技术有限公司|Core network control surface device selection method and device|

---

CN110383867A|2017-03-17|2019-10-25|夏普株式会社|Terminal installation, core network device and communication control method|

---

JP2019525506A|2017-06-19|2019-09-05|華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ．|Registration method, session establishment method, terminal, and AMF entity|

---

CN109803336A|2017-11-17|2019-05-24|华为技术有限公司|Session establishing method and device|

---

WO2019098745A1|2017-11-19|2019-05-23|엘지전자 주식회사|Handover method in wireless communication system and apparatus therefor|

---

US11044773B2|2017-11-30|2021-06-22|At&T Intellectual Property I, L.P.|Dual session packet data network connection|

---

US20190313310A1|2018-04-09|2019-10-10|Nokia Technologies Oy|Session context conversion|

---

US10849035B2|2018-07-26|2020-11-24|EMC IP Holding Company LLC|Sharing of context among base station nodes for mobility management in mobile communications network|

---

KR20200088013A|2019-01-14|2020-07-22|삼성전자주식회사|Electronic device for requesting nssai in wireless communication network and method thereof|

---

WO2021007785A1|2019-07-16|2021-01-21|Oppo广东移动通信有限公司|Policy mapping method and apparatus, and terminal|

---

CN112243279A|2019-07-18|2021-01-19|华为技术有限公司|Method, related device and system for realizing service continuity|

---

CN112333777A|2019-08-05|2021-02-05|中国移动通信有限公司研究院|Mobility processing method, device and equipment|

---

EP3793136A1|2019-09-10|2021-03-17|Orange|Network slicing application access control|

---

KR20210058479A|2019-11-14|2021-05-24|삼성전자주식회사|Apparatus and method for supporting network slices interworking in wireless communication system|

---

CN113163457A|2020-01-22|2021-07-23|北京三星通信技术研究有限公司|Session establishment method, switching method and equipment|

---

KR20220015104A|2020-07-30|2022-02-08|삼성전자주식회사|Method and apparatus for supporting simultaneous use of network slices|

---

US11140618B1|2020-11-04|2021-10-05|Sprint Communications Company L.P.|Wireless data service based on geographic data network names|

---

CN112911573B|2020-12-28|2021-12-14|广州爱浦路网络技术有限公司|Network element discovery method and NRF device for 4G/5G converged networking|

法律状态:
2021-11-23| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

US201762574615P| true| 2017-10-19|2017-10-19|

---

US62/574,615|2017-10-19|

---

US16/117,738|2018-08-30|

---

US16/117,738|US11026128B2|2017-10-19|2018-08-30|Mechanism to enable interworking between network slicing and evolved packet core connectivity|

---

PCT/US2018/049137|WO2019078964A1|2017-10-19|2018-08-31|A mechanism to enable interworking between network slicing and evolved packet core connectivity|

---